Triple
T26515912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 495 in New York |
E669810
|
entity |
| Predicate | urbanRoute |
P52196
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Interstate 495 in New York, urbanRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRoute Context triple: [Interstate 495 in New York, urbanRoute, yes]
-
A.
popularRouteVia
Indicates that a route between two locations commonly or frequently passes through a specified intermediate point or path.
-
B.
isUrbanRoute
chosen
Indicates that a route is located within, passes through, or primarily serves an urban or metropolitan area.
-
C.
cityAlongRoute
Indicates that a given city lies on or is passed through by a specified route or path.
-
D.
directionWithinCity
Indicates a directional relationship specifying where something is located or oriented within the boundaries of a particular city.
-
E.
popularRouteTo
Indicates that one location is widely used or frequently chosen as a route or way to reach another location.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:23 a.m.