Triple
T35295884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Overground (West Croydon) |
E1019366
|
entity |
| Predicate | openedAsOvergroundTerminus |
P90560
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [London Overground (West Croydon), openedAsOvergroundTerminus, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsOvergroundTerminus Context triple: [London Overground (West Croydon), openedAsOvergroundTerminus, 2010]
-
A.
openedAsUndergroundStation
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
B.
openedAsMetrolinkStop
Indicates that a location began operation specifically as a Metrolink transit stop.
-
C.
openedForLondonOverground
chosen
Indicates that something (typically a station or facility) was officially opened specifically for use by the London Overground service.
-
D.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
E.
openedAsSkyTrainStation
Indicates that an entity began operation specifically as a SkyTrain station at the time it was opened.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:03 p.m.