Triple

T25241766
Position Surface form Disambiguated ID Type / Status
Subject Southeastern Idaho E632487 entity
Predicate contains P35 FINISHED
Object Teton River
The Teton River is a tributary of the Henrys Fork of the Snake River in southeastern Idaho, known for its scenic canyon, trout fishing, and the site of the 1976 Teton Dam failure.
E1739962 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: Teton River | Statement: [Southeastern Idaho, contains, Teton River]
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: Teton River
Triple: [Southeastern Idaho, contains, Teton River]
Generated description
The Teton River is a tributary of the Henrys Fork of the Snake River in southeastern Idaho, known for its scenic canyon, trout fishing, and the site of the 1976 Teton Dam failure.

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_69e75a8ec5f88190b9eba06ae42b413a completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47dff233c8190957fdac945808ba4 completed May 1, 2026, 10:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a12090e548c81909177040e13c3f300 completed May 23, 2026, 8:07 p.m.
NEDg Description generation batch_6a120a2acf54819094d2f16637877bb7 completed May 23, 2026, 8:12 p.m.
NED2 Entity disambiguation (via description) batch_6a120b0abaf8819087003d4c7978853f completed May 23, 2026, 8:16 p.m.
Created at: April 21, 2026, 1:07 p.m.