Triple

T34599718
Position Surface form Disambiguated ID Type / Status
Subject Tongue River E888424 entity
Predicate hasTributary P415 FINISHED
Object South Fork Tongue River
The South Fork Tongue River is a mountain stream in north-central Wyoming that flows through the Bighorn National Forest and contributes to the Tongue River watershed.
E888424 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: South Fork Tongue River | Statement: [Tongue River, hasTributary, South Fork Tongue 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: South Fork Tongue River
Triple: [Tongue River, hasTributary, South Fork Tongue River]
Generated description
The South Fork Tongue River is a mountain stream in north-central Wyoming that flows through the Bighorn National Forest and contributes to the Tongue River watershed.

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_69f349d489d48190ba30e7d97c6f5ef9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f72163c748819095edf3a644c54220 completed May 3, 2026, 10:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a375bcc8cf88190a3bdbc86c9d606f3 completed June 21, 2026, 3:34 a.m.
NEDg Description generation batch_6a375c9bba008190abd41299791ed996 completed June 21, 2026, 3:38 a.m.
NED2 Entity disambiguation (via description) batch_6a375d2cf03c819098514298e41adbe7 completed June 21, 2026, 3:40 a.m.
Created at: May 1, 2026, 2:03 a.m.