Triple
T34800789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Cardiff |
E1003212
|
entity |
| Predicate | hasPrimaryRailTerminusInLondon |
P24452
|
FINISHED |
| Object | London Paddington station |
E312600
|
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: London Paddington station | Statement: [London–Cardiff, hasPrimaryRailTerminusInLondon, London Paddington station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRailTerminusInLondon Context triple: [London–Cardiff, hasPrimaryRailTerminusInLondon, London Paddington station]
-
A.
hasLondonUndergroundStation
Indicates that a place or area contains at least one London Underground (Tube) station within its boundaries.
-
B.
primaryLondonTerminal
chosen
Indicates that a given station serves as the main London terminal for a particular rail service or route.
-
C.
hasTerminusInCentralLondon
Indicates that the route, service, or line ends at a terminal point located within Central London.
-
D.
hasRailTerminusInManchester
Indicates that something has its rail terminus (end point of a railway line or service) located in Manchester.
-
E.
originalLondonTerminusLocation
Indicates the location of an entity’s original terminus station in London.
- 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_6a0324c2d618819093f7e6424b0f5baf |
completed | May 12, 2026, 1:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a89e7be88190b295f37f0bbd5edf |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0324292e588190b37d0c3016ea2062 |
completed | May 12, 2026, 12:59 p.m. |
Created at: May 3, 2026, 3:59 p.m.