Triple

T27243381
Position Surface form Disambiguated ID Type / Status
Subject Smoky Hills E687271 entity
Predicate containsReservoir P13043 FINISHED
Object Glen Elder Reservoir
Glen Elder Reservoir is a large man-made lake in north-central Kansas, popular for fishing, boating, and recreation within the Smoky Hills region.
E1960292 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: Glen Elder Reservoir | Statement: [Smoky Hills, containsReservoir, Glen Elder Reservoir]
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: Glen Elder Reservoir
Triple: [Smoky Hills, containsReservoir, Glen Elder Reservoir]
Generated description
Glen Elder Reservoir is a large man-made lake in north-central Kansas, popular for fishing, boating, and recreation within the Smoky Hills region.

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_69ef355547408190b5ca0d777c65040a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f6267ec0788190800c54cc2388370f completed May 2, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2ad20b27fc8190a09e471de8baa4ae completed June 11, 2026, 3:19 p.m.
NEDg Description generation batch_6a2ad2dffa0c819094a5fe98e9f493dc completed June 11, 2026, 3:23 p.m.
NED2 Entity disambiguation (via description) batch_6a2ae095f2e4819092a90aa55fed57c4 completed June 11, 2026, 4:21 p.m.
Created at: April 27, 2026, 10:39 a.m.