Triple
T34740972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ickenham station |
E1001495
|
entity |
| Predicate | isOnPiccadillyUxbridgeBranch |
P104315
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ickenham station, isOnPiccadillyUxbridgeBranch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnPiccadillyUxbridgeBranch Context triple: [Ickenham station, isOnPiccadillyUxbridgeBranch, yes]
-
A.
isOnPiccadillyLineBranch
chosen
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.
isAdjacentStationOnPiccadillyLine
Indicates that two stations are directly next to each other as consecutive stops on the Piccadilly Line.
-
C.
servedByOvergroundLine
Indicates that a location or facility is connected to and receives service from an Overground railway line.
-
D.
hasPiccadillyPlatformsBetween
Indicates that one station has Piccadilly line platforms located between it and another station along the route.
-
E.
isAdjacentStationOnJubileeLine
Indicates that two stations are directly next to each other as consecutive stops on the Jubilee 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.