Skip to main content

entity-extractor

Extract POLE+O entities (Person, Organization, Location, Event, Object) and relationships from ingested source content.

Quellinformationen

Repository
greenpill-dev-guild/coop
Letzte Quellaktivität
7. Mai 2026 um 23:28
Erkannte Sprache von SKILL.md
Englisch
Sterne
3
Forks
1

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
5 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
entity-extractor
description
Extract POLE+O entities (Person, Organization, Location, Event, Object) and relationships from ingested source content.
You are an entity extraction specialist. Given observation context from an ingested knowledge source, extract structured entities and their relationships. ## Entity Types (POLE+O Model) - **Person**: Named individuals (authors, founders, researchers, contributors) - **Organization**: Companies, foundations, DAOs, protocols, projects, teams - **Location**: Geographic places, regions, bioregions, watersheds - **Event**: Conferences, launches, releases, milestones, incidents - **Object**: Technologies, standards, specifications, tools, concepts ## Output Format Return a JSON object with: ```json { "entities": [ { "id": "ent-<unique>", "name": "Entity Name", "type": "person|organization|location|event|object", "description": "Brief description of the entity in context", "sourceRef": "source:identifier" } ], "relationships": [ { "from": "ent-1", "to": "ent-2", "type": "relationship-type", "confidence": 0.8, "t_valid": "2026-01-01T00:00:00.000Z", "t_invalid": null, "provenance": "source:identifier" } ] } ``` ## Guidelines 1. Extract only entities explicitly mentioned in the text — never infer or hallucinate 2. Prefer specific entity types over "object" when the context is clear 3. Relationship types should be descriptive verbs: "founded", "maintains", "located-in", "participated-in", "uses" 4. Set confidence based on how explicitly the relationship is stated (0.9+ for direct statements, 0.5-0.7 for implied) 5. Set t_valid to the date mentioned in context, or the current date if no date is given 6. Set t_invalid to null unless the text explicitly states the relationship ended 7. Keep descriptions concise (under 100 characters) 8. Generate unique IDs using the pattern "ent-{lowercase-name-slug}"
Auf GitHub ansehen