Triple
T20404372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Custom House Elizabeth line station |
E500425
|
entity |
| Predicate | openedForElizabethLine |
P48224
|
FINISHED |
| Object | 24 May 2022 |
—
|
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: 24 May 2022 | Statement: [Custom House Elizabeth line station, openedForElizabethLine, 24 May 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForElizabethLine Context triple: [Custom House Elizabeth line station, openedForElizabethLine, 24 May 2022]
-
A.
openedForLondonOverground
Indicates that something (typically a station or facility) was officially opened specifically for use by the London Overground service.
-
B.
ElizabethLinePlatformsOpened
chosen
Indicates that the platforms associated with the Elizabeth Line have been officially opened for public use.
-
C.
openedForTransilienService
Indicates that a facility or location was officially opened to provide Transilien rail service.
-
D.
openedLondonExtension
Indicates that an entity initiated and made available a new extension or branch located in London.
-
E.
openedOnVictoriaLine
Indicates that something (such as a station or facility) began operation specifically on the Victoria Line.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799161c48190825eca3027d1aa51 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.