Triple
T14426012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churchill Barriers |
E357699
|
entity |
| Predicate | openedToRoadTrafficYear |
P55978
|
FINISHED |
| Object | 1944 |
—
|
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: 1944 | Statement: [Churchill Barriers, openedToRoadTrafficYear, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToRoadTrafficYear Context triple: [Churchill Barriers, openedToRoadTrafficYear, 1944]
-
A.
openedToTrafficInYear
chosen
Indicates the year in which something, typically a transportation facility or route, was first officially opened for public traffic use.
-
B.
openedForYearRoundTraffic
Indicates that something has been made accessible and usable for traffic throughout the entire year, without seasonal closures.
-
C.
openedToRoadTraffic
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
D.
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.
-
E.
roadBypassedInYear
Indicates that a particular road was bypassed or replaced by an alternative route in the specified year.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.