Triple

T27439130
Position Surface form Disambiguated ID Type / Status
Subject Elkhorn River E690874 entity
Predicate hasTributary P415 FINISHED
Object South Fork Elkhorn River
The South Fork Elkhorn River is a tributary stream in northeastern Nebraska that contributes to the flow of the larger Elkhorn River system.
 E1799113 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 Elkhorn River | Statement: [Elkhorn River, hasTributary, South Fork Elkhorn 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 Elkhorn River
Triple: [Elkhorn River, hasTributary, South Fork Elkhorn River]
Generated description
The South Fork Elkhorn River is a tributary stream in northeastern Nebraska that contributes to the flow of the larger Elkhorn River system.

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_69ef5200fa0481908e28508d6e2c149e completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62d8c1af8819097dd3c1bf6704ddd completed May 2, 2026, 4:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b86f2a28819086ea4d6973d95754 completed May 26, 2026, 3:12 p.m.
NEDg Description generation batch_6a15b930d3a48190b47c9a7921d3f9b5 completed May 26, 2026, 3:16 p.m.
NED2 Entity disambiguation (via description) batch_6a15bb82f47c8190bf0ec0ca187e3c4b completed May 26, 2026, 3:25 p.m.
Created at: April 27, 2026, 12:44 p.m.