Triple
T11943352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumberland Park Depot |
E284231
|
entity |
| Predicate | openedForVictoriaLine |
P39712
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Northumberland Park Depot, openedForVictoriaLine, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForVictoriaLine Context triple: [Northumberland Park Depot, openedForVictoriaLine, 1960s]
-
A.
openedOnVictoriaLine
chosen
Indicates that something (such as a station or facility) began operation specifically on the Victoria Line.
-
B.
ElizabethLinePlatformsOpened
Indicates that the platforms associated with the Elizabeth Line have been officially opened for public use.
-
C.
openedForLondonOverground
Indicates that something (typically a station or facility) was officially opened specifically for use by the London Overground service.
-
D.
openedAsMetrolinkLine
Indicates that a railway line or route was inaugurated or began operation specifically as part of the Metrolink network.
-
E.
adjacentStationOnVictoriaLine
Indicates that one station is directly next to another station along the Victoria Line, with no other stations in between.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9034444488190925a6fa6c856ed08 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.