Triple
T25738412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadcaster Bridge |
E648142
|
entity |
| Predicate | closedToTrafficFrom |
P120271
|
FINISHED |
| Object | 2015-12-29 |
—
|
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: 2015-12-29 | Statement: [Tadcaster Bridge, closedToTrafficFrom, 2015-12-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToTrafficFrom Context triple: [Tadcaster Bridge, closedToTrafficFrom, 2015-12-29]
-
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.
closedToMotorTraffic
Indicates that a route, road, or path is not accessible for use by motor vehicles.
-
C.
closedToAllTraffic
chosen
Indicates that the subject is not accessible or usable by any type of traffic.
-
D.
closedToScheduledTraffic
Indicates that an infrastructure element (such as a road, runway, or route) is not available for use by regular, planned, or scheduled traffic.
-
E.
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.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 3:37 a.m.