Triple

T21094140
Position Surface form Disambiguated ID Type / Status
Subject Interstate 690 E519715 entity
Predicate connectsTo P845 FINISHED
Object New York State Route 695
New York State Route 695 is a short north–south state highway in the Syracuse area that serves as a connector between Interstate 690 and New York State Route 5.
E2284978 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 695 | Statement: [Interstate 690, connectsTo, New York State Route 695]
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 695
Triple: [Interstate 690, connectsTo, New York State Route 695]
Generated description
New York State Route 695 is a short north–south state highway in the Syracuse area that serves as a connector between Interstate 690 and New York State Route 5.

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_69e0b507dd9081908fb8bfcbef4c8b46 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e709517a18819081ede1d38e2c4391 completed April 21, 2026, 5:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a44b3916758819092544ab28c7b5afa completed July 1, 2026, 6:28 a.m.
NEDg Description generation batch_6a44b587c3ec8190997b70be1d8c7c15 completed July 1, 2026, 6:36 a.m.
NED2 Entity disambiguation (via description) batch_6a44b5e52690819086e95e560158612c completed July 1, 2026, 6:38 a.m.
Created at: April 16, 2026, 2:51 p.m.