Triple
T7265659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Scotsman |
E159766
|
entity |
| Predicate | heritageRailwayUse |
P76034
|
FINISHED |
| Object | mainline excursions |
—
|
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: mainline excursions | Statement: [Flying Scotsman, heritageRailwayUse, mainline excursions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageRailwayUse Context triple: [Flying Scotsman, heritageRailwayUse, mainline excursions]
-
A.
railwayHeritageFeature
Indicates that something is a feature associated with railway heritage, such as historically significant railway structures, equipment, or related elements.
-
B.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
C.
openedAsHeritageRailway
Indicates that a railway line or route was reopened specifically for heritage or tourist purposes rather than for regular commercial transport service.
-
D.
heritageRailwayName
Indicates the specific name assigned to a heritage railway associated with an entity.
-
E.
formerRailUse
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:57 p.m.