Triple
T34674219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Meteor route |
E890453
|
entity |
| Predicate | hasTrainName |
P138983
|
FINISHED |
| Object | Silver Meteor |
—
|
NE NERFINISHED |
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: Silver Meteor | Statement: [Silver Meteor route, hasTrainName, Silver Meteor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainName Context triple: [Silver Meteor route, hasTrainName, Silver Meteor]
-
A.
railwayName
Indicates the name assigned to a specific railway or railway line in the relationship.
-
B.
hasTrainIdentification
Indicates that an entity is associated with a specific train identification code or number used to uniquely identify that train.
-
C.
servedByNamedTrain
chosen
Indicates that a service, route, or journey is operated specifically by a train with a particular designated name.
-
D.
hasRailOperatorNamedAfter
Indicates that a rail operator is named after the specified entity.
-
E.
usesTrainNumber
Indicates that one entity operates, identifies, or references another entity by a specific train number.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: May 1, 2026, 2:05 a.m.