Triple
T37531401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoney Nakoda Nations |
E933055
|
entity |
| Predicate | hasCollectiveCouncil |
P38155
|
FINISHED |
| Object | Stoney Nakoda Nations council |
E933055
|
NE 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: Stoney Nakoda Nations council | Statement: [Stoney Nakoda Nations, hasCollectiveCouncil, Stoney Nakoda Nations council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveCouncil Context triple: [Stoney Nakoda Nations, hasCollectiveCouncil, Stoney Nakoda Nations council]
-
A.
hasCouncilStructure
Indicates that an entity is organized or governed according to a specific council-based structure or system.
-
B.
councilCan
Indicates that a council has the authority or permission to perform a specified action or exercise a particular power.
-
C.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
D.
hasCommunityCouncil
chosen
Indicates that an entity is governed, represented, or overseen by a community council.
-
E.
hasCouncilChambers
Indicates that an entity possesses or contains designated rooms or facilities used for council meetings or deliberations.
- F. None of above.
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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417107452481908ecaf3a4c1767be4 |
completed | June 28, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.