Triple
T24297077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Coast |
E605988
|
entity |
| Predicate | operatedClassOfTrain |
P67417
|
FINISHED |
| Object | InterCity 125 |
—
|
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: InterCity 125 | Statement: [East Coast, operatedClassOfTrain, InterCity 125]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedClassOfTrain Context triple: [East Coast, operatedClassOfTrain, InterCity 125]
-
A.
operatedRollingStockClass
chosen
Indicates that an entity (such as a company or operator) has operated a specific class or type of rolling stock (e.g., trains or rail vehicles).
-
B.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
C.
railwayClass
Indicates the specific classification or category assigned to a railway or railway service within a defined system.
-
D.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
-
E.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915ada688190aa9c4bdaa2f1617f |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.