Triple
T2933190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wargandí |
E79201
|
entity |
| Predicate | autonomyType |
P5525
|
FINISHED |
| Object | indigenous autonomy |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: indigenous autonomy | Statement: [Wargandí, autonomyType, indigenous autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomyType Context triple: [Wargandí, autonomyType, indigenous autonomy]
-
A.
autonomyStatus
Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
-
B.
hasAutonomyWithin
Indicates that one entity possesses independent decision-making power or self-governance within the scope, domain, or boundaries defined by another entity.
-
C.
grantsOfAutonomy
Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
-
D.
typeOfIndependence
chosen
Indicates the specific nature or category of independence that applies to an entity or relationship.
-
E.
hasLimitedAutonomyIn
Indicates that an entity operates or makes decisions within a domain where its freedom of action is constrained or controlled by another entity or governing context.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983a4ae08190aa1aeb2747abd1a1 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.