Triple
T34800788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Cardiff |
E1003212
|
entity |
| Predicate | hasPrimaryRailOperator |
P121930
|
FINISHED |
| Object | Great Western Railway |
E28420
|
NE 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: Great Western Railway | Statement: [London–Cardiff, hasPrimaryRailOperator, Great Western Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRailOperator Context triple: [London–Cardiff, hasPrimaryRailOperator, Great Western Railway]
-
A.
hasRailTransportOperator
chosen
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
B.
hasLocalRailOperator
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
-
C.
hasRailOperatorNamedAfter
Indicates that a rail operator is named after the specified entity.
-
D.
hasNearbyRailwayOperator
Indicates that a railway operator is located close to or serves the vicinity of a given entity.
-
E.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
- F. None of above.
Provenance (4 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a03232efd8481908ee25447a29ee20b |
completed | May 12, 2026, 12:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fabe43c8190803d59ef868042d0 |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a032269dcb08190907c965c28145b77 |
completed | May 12, 2026, 12:51 p.m. |
Created at: May 3, 2026, 3:59 p.m.