Triple
T24966003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eskasoni First Nation |
E624743
|
entity |
| Predicate | hasBandGovernmentType |
P130835
|
FINISHED |
| Object | Band council |
—
|
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: Band council | Statement: [Eskasoni First Nation, hasBandGovernmentType, Band council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandGovernmentType Context triple: [Eskasoni First Nation, hasBandGovernmentType, Band council]
-
A.
hasBandGovernment
Indicates that a band is governed or administered by a particular governing body or authority.
-
B.
hasGovernmentalBodyType
chosen
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
C.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
D.
hasGovernmentTypeCountry
Indicates that a country possesses or is characterized by a particular form or type of government.
-
E.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6 a.m.