Triple
T26623060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP 4268 |
E668256
|
entity |
| Predicate | heritageRailUse |
P76034
|
FINISHED |
| Object | excursion trains |
—
|
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: excursion trains | Statement: [SP 4268, heritageRailUse, excursion trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageRailUse Context triple: [SP 4268, heritageRailUse, excursion trains]
-
A.
heritageRailwayUse
chosen
Indicates that a railway line, infrastructure, or service is used for heritage or historical purposes rather than for regular commercial transport.
-
B.
heritageRailwayType
Indicates the specific kind or classification of a heritage railway associated with an entity.
-
C.
railwayHeritageFrom
Indicates that something derives its historical or cultural significance from a particular railway or railway-related source.
-
D.
railwayHeritageFeature
Indicates that something is a feature associated with railway heritage, such as historically significant railway structures, equipment, or related elements.
-
E.
formerRailUse
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:21 a.m.