Triple
T23646569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opaskwayak Cree Nation |
E584052
|
entity |
| Predicate | hasSelfGovernance |
P26412
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Opaskwayak Cree Nation, hasSelfGovernance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelfGovernance Context triple: [Opaskwayak Cree Nation, hasSelfGovernance, true]
-
A.
selfGovernedBy
Indicates that an entity independently controls and manages itself without external governance.
-
B.
selfGoverning
chosen
Indicates that an entity has the authority and capacity to govern, regulate, and manage itself independently, without external control.
-
C.
hasLocalSelfGovernment
Indicates that an entity possesses its own local governing authority with decision-making powers over local affairs.
-
D.
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.
-
E.
hasAutonomyStatute
Indicates that an entity is governed by or subject to a specific autonomy statute defining its self-governing powers or autonomous status.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28571bc8190b3f7275068d19320 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.