Triple
T26742099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 88 in New York |
E674288
|
entity |
| Predicate | terminusInterchangeWith |
P73851
|
FINISHED |
| Object | I-81 near Binghamton |
—
|
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: I-81 near Binghamton | Statement: [Interstate 88 in New York, terminusInterchangeWith, I-81 near Binghamton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusInterchangeWith Context triple: [Interstate 88 in New York, terminusInterchangeWith, I-81 near Binghamton]
-
A.
hasInterchangesWith
chosen
Indicates that two transportation routes, lines, or services share one or more points where passengers can transfer between them.
-
B.
isInterchangeWith
Indicates that two entities can be substituted or exchanged for one another without loss of function, value, or compatibility.
-
C.
terminusWestConnection
Indicates that one entity serves as the western endpoint where it connects to another entity or route.
-
D.
interchangeStation
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
-
E.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:49 a.m.