Triple

T25546425
Position Surface form Disambiguated ID Type / Status
Subject South Pulaski Road E640317 entity
Predicate intersects P1018 FINISHED
Object West 111th Street
West 111th Street is a major east–west thoroughfare on Chicago’s South Side, running through multiple neighborhoods and serving as a key local commercial and commuter route.
E1763030 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: West 111th Street | Statement: [South Pulaski Road, intersects, West 111th Street]
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: West 111th Street
Triple: [South Pulaski Road, intersects, West 111th Street]
Generated description
West 111th Street is a major east–west thoroughfare on Chicago’s South Side, running through multiple neighborhoods and serving as a key local commercial and commuter route.

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_69e75dc101a881909fd33b02174e9768 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8992ce881909b95d520f580e231 completed May 2, 2026, 1:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12623e73ec81908eca8d3f74874997 completed May 24, 2026, 2:28 a.m.
NEDg Description generation batch_6a126440683881909b462092139a79cf completed May 24, 2026, 2:36 a.m.
NED2 Entity disambiguation (via description) batch_6a1264a5d7748190902dbe10317c00a8 completed May 24, 2026, 2:38 a.m.
Created at: April 21, 2026, 3:34 p.m.