Triple
T18216234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Route 263 |
E436165
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | NY 263 |
—
|
NE NERFINISHED |
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: NY 263 | Statement: [New York State Route 263, abbreviation, NY 263]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NY 263 Context triple: [New York State Route 263, abbreviation, NY 263]
-
A.
NY 306
NY 306 is a state highway in Rockland County, New York, serving as a local north–south route through suburban communities.
-
B.
NY 352
NY 352 is a state highway in New York that serves as an east–west route connecting communities in the Southern Tier region.
-
C.
New York State Route 265
New York State Route 265 is a north–south state highway in western New York that runs through the Buffalo–Niagara Falls area, serving communities such as Tonawanda.
-
D.
NY 128
NY 128 is a state highway in New York that serves as a local connector route in Westchester County.
-
E.
New York State Route 263
chosen
New York State Route 263 is a state highway in Erie County, New York, serving as a key local connector through the Buffalo suburbs, including the Amherst area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47765a081908d0bbca1245f89ba |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 10:32 a.m.