Triple

T30704065
Position Surface form Disambiguated ID Type / Status
Subject Kaskaskia River E781703 entity
Predicate hasFloodControlStructure P25010 FINISHED
Object Shelbyville Dam
Shelbyville Dam is a major flood-control and water-management structure on the Kaskaskia River in Illinois, forming Lake Shelbyville and supporting regional recreation and water supply.
E2283730 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: Shelbyville Dam | Statement: [Kaskaskia River, hasFloodControlStructure, Shelbyville Dam]
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: Shelbyville Dam
Triple: [Kaskaskia River, hasFloodControlStructure, Shelbyville Dam]
Generated description
Shelbyville Dam is a major flood-control and water-management structure on the Kaskaskia River in Illinois, forming Lake Shelbyville and supporting regional recreation and water supply.

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_69f224abfcf081909492e64d3cc35262 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68c191778819093c79b1b785fbc39 completed May 2, 2026, 11:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a42ca79ebf481908044fdf58853507a completed June 29, 2026, 7:41 p.m.
NEDg Description generation batch_6a42cb5bec408190afe06e29e3feea7b completed June 29, 2026, 7:45 p.m.
NED2 Entity disambiguation (via description) batch_6a42dcda915c8190ae695a1363ed8d22 completed June 29, 2026, 9 p.m.
Created at: April 29, 2026, 8:34 p.m.