Triple
T36830914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piikani Indian Reserve No. 147 |
E910135
|
entity |
| Predicate | hasPrimaryRoleFor |
P14496
|
FINISHED |
| Object | Piikani Nation |
E264567
|
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: Piikani Nation | Statement: [Piikani Indian Reserve No. 147, hasPrimaryRoleFor, Piikani Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRoleFor Context triple: [Piikani Indian Reserve No. 147, hasPrimaryRoleFor, Piikani Nation]
-
A.
hasPrimaryRoleInComplex
Indicates that an entity serves as the main or principal functional component within a larger complex.
-
B.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
hasPrimaryAccessRole
Indicates that an entity is assigned the main or most authoritative access role governing its permissions or privileges.
-
D.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efda3d6b08190bff513454663f404 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.