Triple
T8297157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Route 13 |
E194247
|
entity |
| Predicate | adjacentStateRoute |
P82589
|
FINISHED |
| Object | New Hampshire Route 13 at the state line |
—
|
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: New Hampshire Route 13 at the state line | Statement: [Massachusetts Route 13, adjacentStateRoute, New Hampshire Route 13 at the state line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentStateRoute Context triple: [Massachusetts Route 13, adjacentStateRoute, New Hampshire Route 13 at the state line]
-
A.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
B.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
C.
adjacentStationOnLine
Indicates that one station is directly next to another station along the same transit line, with no other station in between.
-
D.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
E.
adjacentToStation
Indicates that one entity is located next to or immediately beside a station.
- F. None of above. chosen
Provenance (4 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7df887148190bddc2609bc885cb4 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:53 p.m.