Triple
T26742101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 88 in New York |
E674288
|
entity |
| Predicate | routeNumbering |
P21547
|
FINISHED |
| Object | odd-numbered auxiliary Interstate |
—
|
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: odd-numbered auxiliary Interstate | Statement: [Interstate 88 in New York, routeNumbering, odd-numbered auxiliary Interstate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNumbering Context triple: [Interstate 88 in New York, routeNumbering, odd-numbered auxiliary Interstate]
-
A.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
B.
routeNumberFormat
chosen
Indicates how the identifying number or code for a route is structured or formatted.
-
C.
routeNumberingAuthority
Indicates the authority or organization responsible for assigning and managing the official number designation of a route.
-
D.
roadNumberIncludes
Indicates that a road’s identifier or designation contains the specified number or numeric sequence.
-
E.
roadNumberType
Indicates the classification or type category assigned to a road’s identifying number (e.g., highway, route, local road).
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 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, 3:49 a.m.