Triple
T25864018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoke Bank |
E651561
|
entity |
| Predicate | worldRecordTrainType |
P56947
|
FINISHED |
| Object | steam‑hauled express train |
—
|
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‑hauled express train | Statement: [Stoke Bank, worldRecordTrainType, steam‑hauled express train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRecordTrainType Context triple: [Stoke Bank, worldRecordTrainType, steam‑hauled express train]
-
A.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
-
B.
trainTypeUsed
chosen
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
C.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
D.
primaryLocomotiveType
Indicates the main method or mechanism by which an entity typically moves or travels.
-
E.
laterLocomotiveType
Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 22, 2026, 8:06 a.m.