Triple
T10856754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashton Canal aqueduct |
E256286
|
entity |
| Predicate | openToTraffic |
P16836
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ashton Canal aqueduct, openToTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openToTraffic Context triple: [Ashton Canal aqueduct, openToTraffic, yes]
-
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.
openedToRoadTraffic
chosen
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
C.
reopenedToTraffic
Indicates that a previously closed route or transportation facility has been opened again for use by traffic.
-
D.
openedToCivilianTraffic
Indicates that a previously restricted or closed route, facility, or infrastructure has been made accessible for use by civilian (non-military) traffic.
-
E.
openedToGoodsTraffic
Indicates that a route, facility, or infrastructure was officially made available for the movement and handling of goods or freight 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7513695ac8190b5812e977a422c37 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.