Triple
T19076767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ktunaxa language |
E466924
|
entity |
| Predicate | statusInBritishColumbia |
P33417
|
FINISHED |
| Object | recognized Indigenous language |
—
|
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: recognized Indigenous language | Statement: [Ktunaxa language, statusInBritishColumbia, recognized Indigenous language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInBritishColumbia Context triple: [Ktunaxa language, statusInBritishColumbia, recognized Indigenous language]
-
A.
legalStatusCanada
Indicates the legal classification or standing of an entity under Canadian law.
-
B.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
-
C.
statusInRegion
chosen
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e5591081908a4f8e4b2011b408 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.