Triple
T21349938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayners Lane station |
E526447
|
entity |
| Predicate | piccadillyLineServiceIntroduced |
P45272
|
FINISHED |
| Object | 1933-10-23 |
—
|
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: 1933-10-23 | Statement: [Rayners Lane station, piccadillyLineServiceIntroduced, 1933-10-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: piccadillyLineServiceIntroduced Context triple: [Rayners Lane station, piccadillyLineServiceIntroduced, 1933-10-23]
-
A.
isOnPiccadillyLineBranch
Indicates that something (typically a station or track segment) lies on a branch of the Piccadilly Line rather than on its main central section.
-
B.
piccadillyLinePlatformsOpened
chosen
Indicates that the platforms serving the Piccadilly line at a station have been opened for use.
-
C.
hasPiccadillyPlatformsBetween
Indicates that one station has Piccadilly line platforms located between it and another station along the route.
-
D.
hasPiccadillyLinePlatforms
Indicates that an entity has platforms served by the Piccadilly Line.
-
E.
ElizabethLinePlatformsOpened
Indicates that the platforms associated with the Elizabeth Line have been officially opened for public use.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad30512081909012ce318fa67679 |
completed | April 22, 2026, 11:12 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:03 p.m.