Triple
T29555354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping Ongar Railway |
E749887
|
entity |
| Predicate | heritageRollingStockType |
P159745
|
FINISHED |
| Object | steam locomotives |
—
|
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: steam locomotives | Statement: [Epping Ongar Railway, heritageRollingStockType, steam locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageRollingStockType Context triple: [Epping Ongar Railway, heritageRollingStockType, steam locomotives]
-
A.
notableRollingStock
Indicates that there is a notable or historically significant piece of rolling stock (such as a train car or locomotive) associated with the subject.
-
B.
heritageRailwayType
chosen
Indicates the specific kind or classification of a heritage railway associated with an entity.
-
C.
eraOfRollingStock
Indicates the historical time period or service era during which a particular rolling stock type was in use.
-
D.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
E.
branchLineRollingStock
Indicates that the rolling stock is assigned to or operates on a branch line rather than a main line.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 5:15 p.m.