Triple

T17927832
Position Surface form Disambiguated ID Type / Status
Subject New York State Route 277 E448242 entity
Predicate hasJunctionWith P1018 FINISHED
Object New York State Route 391
New York State Route 391 is a north–south state highway in western New York that serves as a connector between local communities and major regional routes south of Buffalo.
E2057902 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: New York State Route 391 | Statement: [New York State Route 277, hasJunctionWith, New York State Route 391]
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: New York State Route 391
Triple: [New York State Route 277, hasJunctionWith, New York State Route 391]
Generated description
New York State Route 391 is a north–south state highway in western New York that serves as a connector between local communities and major regional routes south of Buffalo.

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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a5505af88190aa7a5cfee0baa3a4 completed April 19, 2026, 9:50 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35afadcce881909baf642901f3998e completed June 19, 2026, 9:07 p.m.
NEDg Description generation batch_6a35b3e0e458819084da74918e1e448c completed June 19, 2026, 9:25 p.m.
NED2 Entity disambiguation (via description) batch_6a35b44270e08190b66305de4a5c0bb8 completed June 19, 2026, 9:27 p.m.
Created at: April 10, 2026, 10:20 a.m.