Triple
T11724395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greyhound Bridge |
E278721
|
entity |
| Predicate | closedToTrafficDuringRepairs |
P101001
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Greyhound Bridge, closedToTrafficDuringRepairs, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToTrafficDuringRepairs Context triple: [Greyhound Bridge, closedToTrafficDuringRepairs, 2018]
-
A.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
B.
closedToCivilianTraffic
Indicates that access along a route or at a location is restricted so that civilian vehicles or pedestrians are not allowed to use it.
-
C.
closedToCommercialTrafficDate
Indicates the date on which something (typically a route, facility, or area) was officially closed to commercial traffic.
-
D.
reopenedToTraffic
Indicates that a previously closed route or transportation facility has been opened again for use by traffic.
-
E.
roadClosesIn
Indicates that a road becomes closed or inaccessible within a specified location, area, or boundary.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d603cc8190b2e68d0bdd793362 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.