Triple

T30837243
Position Surface form Disambiguated ID Type / Status
Subject Wood River, Illinois E785397 entity
Predicate locatedOn P40 FINISHED
Object Wood River
Wood River is a city in Madison County, Illinois, known historically as an industrial and refinery town along the Mississippi River near the St. Louis metropolitan area.
 E2042201 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: Wood River | Statement: [Wood River, Illinois, locatedOn, Wood 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: Wood River
Triple: [Wood River, Illinois, locatedOn, Wood River]
Generated description
Wood River is a city in Madison County, Illinois, known historically as an industrial and refinery town along the Mississippi River near the St. Louis metropolitan area.

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_69f224b73d8c81908129383bfb397c87 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6913f9c4c8190b5984101070d067c completed May 3, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a352f9515b88190af5307bf01f999fa completed June 19, 2026, 12:01 p.m.
NEDg Description generation batch_6a3530781f548190b29ceca0c6dcf672 completed June 19, 2026, 12:05 p.m.
NED2 Entity disambiguation (via description) batch_6a35325acae0819090ed2b885836836d completed June 19, 2026, 12:13 p.m.
Created at: April 29, 2026, 8:45 p.m.