Triple
T31560798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Croix Crossing |
E805256
|
entity |
| Predicate | openedToMotorVehicles |
P16836
|
FINISHED |
| Object | 2017-08-02 |
—
|
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: 2017-08-02 | Statement: [St. Croix Crossing, openedToMotorVehicles, 2017-08-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToMotorVehicles Context triple: [St. Croix Crossing, openedToMotorVehicles, 2017-08-02]
-
A.
openedForThroughTraffic
Indicates that a route or segment is available and accessible for vehicles to pass through (not just for local access), allowing continuous through traffic.
-
B.
openedAsMotorway
Indicates that a road segment was initially opened to traffic specifically as a motorway.
-
C.
openedToRoadTraffic
chosen
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
D.
openedToPassengerTraffic
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
-
E.
wasOpenToVehicularTrafficUntil
Indicates that a route or roadway permitted vehicular traffic up to a specific end time or date, after which such traffic was no longer allowed.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 30, 2026, 10:15 p.m.