Triple
T8279131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nipissing First Nation |
E193621
|
entity |
| Predicate | hasGovernancePriority |
P82478
|
FINISHED |
| Object | self-determination |
—
|
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: self-determination | Statement: [Nipissing First Nation, hasGovernancePriority, self-determination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernancePriority Context triple: [Nipissing First Nation, hasGovernancePriority, self-determination]
-
A.
hasGovernanceLevel
Indicates the degree or tier of authority, control, or decision-making power that an entity holds within a governance structure.
-
B.
hasPriorityAt
Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
-
C.
governsAfter
Indicates that one entity assumes governing authority or control after another entity’s period of governance has ended.
-
D.
hasLocalGovernanceType
Indicates the specific form or system of local governance that applies to an entity.
-
E.
hasLocalGovernanceRole
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
- F. None of above. chosen
Provenance (4 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ece5708190a1569bcfad5b3644 |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:51 p.m.