Triple
T24492377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodhead Tunnels |
E617675
|
entity |
| Predicate | closureOfWoodheadLine |
P95264
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Woodhead Tunnels, closureOfWoodheadLine, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureOfWoodheadLine Context triple: [Woodhead Tunnels, closureOfWoodheadLine, 1981]
-
A.
railLineClosed
chosen
Indicates that a railway line has been officially taken out of service and is no longer operational for train traffic.
-
B.
railwayWorksClosed
Indicates that a railway workshop, depot, or related railway works facility has ceased operations or been officially closed.
-
C.
reopenedAsPassengerLine
Indicates that a previously closed or differently used railway line has been opened again specifically for passenger services.
-
D.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
E.
lineClosedToFreight
Indicates that a railway line is not available for freight services or freight train operations.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.