Triple
T27208492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 490 (New York) |
E683936
|
entity |
| Predicate | isBeltwayFor |
P9042
|
FINISHED |
| Object | Rochester, New York |
—
|
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: Rochester, New York | Statement: [Interstate 490 (New York), isBeltwayFor, Rochester, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBeltwayFor Context triple: [Interstate 490 (New York), isBeltwayFor, Rochester, New York]
-
A.
BeltwayRefersTo
Indicates that one entity is referred to as a "beltway" in relation to another, typically denoting a ring road or circumferential route associated with that entity.
-
B.
beltwayDesignation
Indicates that a roadway has been designated as part of a beltway or ring road encircling an area.
-
C.
beltwayAround
chosen
Indicates that one roadway or route functions as a beltway encircling or surrounding another specified area or location.
-
D.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
-
E.
beltwayName
Indicates that a beltway (ring road or orbital highway) has a specific name.
- F. None of above.
Provenance (3 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625e6cd708190aea9dc220df25717 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:38 a.m.