Triple

T26266053
Position Surface form Disambiguated ID Type / Status
Subject Tahltan people E656985 entity
Predicate mainCommunity P6194 FINISHED
Object Iskut, British Columbia
Iskut, British Columbia is a remote Indigenous community in northwestern British Columbia that serves as one of the primary settlements of the Tahltan people.
E1726920 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: Iskut, British Columbia | Statement: [Tahltan people, mainCommunity, Iskut, British Columbia]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Iskut, British Columbia
Triple: [Tahltan people, mainCommunity, Iskut, British Columbia]
Generated description
Iskut, British Columbia is a remote Indigenous community in northwestern British Columbia that serves as one of the primary settlements of the Tahltan people.

Provenance (5 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_69ee5b4e21bc819082be98bc9ab09796 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f60e047d0081909bbc4d4324d93578 completed May 2, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11bb001b948190a969e6d8820b3708 completed May 23, 2026, 2:34 p.m.
NEDg Description generation batch_6a11bb97c4208190aae3433b12358750 completed May 23, 2026, 2:37 p.m.
NED2 Entity disambiguation (via description) batch_6a11be83120c819096ca5fc2f18a4739 completed May 23, 2026, 2:49 p.m.
Created at: April 26, 2026, 9:11 p.m.