Triple
T24779308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenglass and Eskdale Railway |
E619947
|
entity |
| Predicate | reopenedAsNarrowGauge |
P157301
|
FINISHED |
| Object | 1915 |
—
|
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: 1915 | Statement: [Ravenglass and Eskdale Railway, reopenedAsNarrowGauge, 1915]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsNarrowGauge Context triple: [Ravenglass and Eskdale Railway, reopenedAsNarrowGauge, 1915]
-
A.
reopenedAsPassengerLine
Indicates that a previously closed or differently used railway line has been opened again specifically for passenger services.
-
B.
reopenedAsElectrifiedDoubleTrack
Indicates that a previously closed or non-electrified/single-track railway line was reopened after being upgraded to an electrified double-track configuration.
-
C.
openedAsRailroad
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
-
D.
openedAsWagonRoad
Indicates that a route or path was originally established and used as a wagon road.
-
E.
reopenedAsAmtrakStation
Indicates that a previously closed station was reopened specifically to serve as an Amtrak station.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f42b11251881908070b93355de64ad |
completed | May 1, 2026, 4:24 a.m. |
Created at: April 18, 2026, 4:43 a.m.