Triple
T10857948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East London line |
E256317
|
entity |
| Predicate | reopenedAsLondonOverground |
P96104
|
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: [East London line, reopenedAsLondonOverground, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsLondonOverground Context triple: [East London line, reopenedAsLondonOverground, 2010]
-
A.
openedForLondonOverground
Indicates that something (typically a station or facility) was officially opened specifically for use by the London Overground service.
-
B.
reopenedAsMetroStation
Indicates that a previously closed or differently used station was later reopened specifically as a metro station.
-
C.
transferredToLondonUnderground
Indicates that something or someone has been moved from a previous context or system into the London Underground network or organization.
-
D.
reopenedAsSubwayStation
Indicates that a previously closed or differently used station has been opened again specifically as a subway station.
-
E.
ElizabethLinePlatformsOpened
Indicates that the platforms associated with the Elizabeth Line have been officially opened for public use.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.