Triple
T4441515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Numbered Route 3 corridor between Boston and New Hampshire |
E95780
|
entity |
| Predicate | followsHighway |
P56524
|
FINISHED |
| Object | U.S. Route 3 |
—
|
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: U.S. Route 3 | Statement: [U.S. Numbered Route 3 corridor between Boston and New Hampshire, followsHighway, U.S. Route 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsHighway Context triple: [U.S. Numbered Route 3 corridor between Boston and New Hampshire, followsHighway, U.S. Route 3]
-
A.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
C.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
D.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
E.
withinDrivingRoute
Indicates that one location can be reached from another via a practical or allowable driving route, typically within a reasonable distance or time.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355ad71588190b1dcad4250472c29 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:32 p.m.