Triple
T2095491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 110 (Florida) |
E32770
|
entity |
| Predicate | openedForTrafficApprox |
P16836
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Interstate 110 (Florida), openedForTrafficApprox, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForTrafficApprox Context triple: [Interstate 110 (Florida), openedForTrafficApprox, 1960s]
-
A.
openedToRoadTraffic
chosen
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
B.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
C.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
D.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
-
E.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba99ddc48190bb2097b56efb7aca |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.