Triple

T16094028
Position Surface form Disambiguated ID Type / Status
Subject Skokie Highway E390433 entity
Predicate hasJunctionWith P1018 FINISHED
Object Dundee Road
Dundee Road is a major east–west arterial street in the northern suburbs of Chicago, Illinois, serving as a key connector through communities such as Northbrook, Wheeling, and Deerfield.
E1624353 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: Dundee Road | Statement: [Skokie Highway, hasJunctionWith, Dundee Road]
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: Dundee Road
Triple: [Skokie Highway, hasJunctionWith, Dundee Road]
Generated description
Dundee Road is a major east–west arterial street in the northern suburbs of Chicago, Illinois, serving as a key connector through communities such as Northbrook, Wheeling, and Deerfield.

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_69d87f198bc48190a8b7e53ca15b7ead completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e1859196808190ae30b4f7c1641eed completed April 17, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbcd6237c8190815702e274a30c44 completed May 22, 2026, 2:17 a.m.
NEDg Description generation batch_6a0fbddd0ccc81908036002270cbf4f5 completed May 22, 2026, 2:22 a.m.
NED2 Entity disambiguation (via description) batch_6a0fbf3cf7988190a9d766bfca4ef994 completed May 22, 2026, 2:28 a.m.
Created at: April 10, 2026, 4:59 a.m.