Triple
T9772578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Underground station |
E237161
|
entity |
| Predicate | openedForLondonOverground |
P90560
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Richmond Underground station, openedForLondonOverground, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForLondonOverground Context triple: [Richmond Underground station, openedForLondonOverground, 2011]
-
A.
ElizabethLinePlatformsOpened
Indicates that the platforms associated with the Elizabeth Line have been officially opened for public use.
-
B.
piccadillyLinePlatformsOpened
Indicates that the platforms serving the Piccadilly line at a station have been opened for use.
-
C.
openedAsUndergroundStation
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
D.
openedOnVictoriaLine
Indicates that something (such as a station or facility) began operation specifically on the Victoria Line.
-
E.
primaryLondonTerminal
Indicates that a given station serves as the main London terminal for a particular rail service or route.
- F. None of above. chosen
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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f5261481908d9bac8c43da5294 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:26 p.m.