Triple
T21283407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 86 |
E524588
|
entity |
| Predicate | followsFormerRoute |
P102403
|
FINISHED |
| Object | New York State Route 17 |
—
|
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: New York State Route 17 | Statement: [Interstate 86, followsFormerRoute, New York State Route 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsFormerRoute Context triple: [Interstate 86, followsFormerRoute, New York State Route 17]
-
A.
usesFormerRouteOf
chosen
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
-
B.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
C.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
D.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
E.
isPrecededOnRouteBy
Indicates that one element on a route comes immediately before another in the ordered sequence of that route.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d3dfbc819081bd876d95c7c480 |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.