Triple

T20703518
Position Surface form Disambiguated ID Type / Status
Subject Dane-zaa E508840 entity
Predicate hasBandGovernment P67098 FINISHED
Object Prophet River First Nation
Prophet River First Nation is a Dane-zaa (Beaver) Indigenous community and governing body located in northeastern British Columbia, Canada.
E1890445 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: Prophet River First Nation | Statement: [Dane-zaa, hasBandGovernment, Prophet River First Nation]
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: Prophet River First Nation
Triple: [Dane-zaa, hasBandGovernment, Prophet River First Nation]
Generated description
Prophet River First Nation is a Dane-zaa (Beaver) Indigenous community and governing body located in northeastern British Columbia, Canada.

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_69e0b4c2b2a481909e31e9cb8f81ab55 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6c18dbda081908217dcb61cbf7ba4 completed April 21, 2026, 12:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a26f19ad7c48190b01dfaea5f71b7bd completed June 8, 2026, 4:45 p.m.
NEDg Description generation batch_6a26f66b547081909ac88e14bf340493 completed June 8, 2026, 5:05 p.m.
NED2 Entity disambiguation (via description) batch_6a26f7d1e25481909fbe21144c0c22b6 completed June 8, 2026, 5:11 p.m.
Created at: April 16, 2026, 12:13 p.m.