Triple
T20025314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katzie Indian Reserve No. 1 |
E494965
|
entity |
| Predicate | hasBandOfficeOf |
P138415
|
FINISHED |
| Object | Katzie First Nation |
—
|
NE NERFINISHED |
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: Katzie First Nation | Statement: [Katzie Indian Reserve No. 1, hasBandOfficeOf, Katzie First Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandOfficeOf Context triple: [Katzie Indian Reserve No. 1, hasBandOfficeOf, Katzie First Nation]
-
A.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the specified place.
-
B.
hasOperatorHeadquartersIn
Indicates that the primary operational headquarters of an operator is located in a specified place.
-
C.
hasHindquartersOf
Indicates that one entity possesses or exhibits the hindquarters characteristic or form of another entity.
-
D.
hasHeadquartersOn
Indicates that an organization’s main headquarters is located on a specified street, road, or similar thoroughfare.
-
E.
hasHeadquartersRoleFor
Indicates that an entity holds a specific role or position within the headquarters of another entity.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628d5b8c8190a35f95ac4a016550 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:35 p.m.