Triple
T7654003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embankment station |
E173328
|
entity |
| Predicate | isCentralLondonInterchange |
P15947
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Embankment station, isCentralLondonInterchange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralLondonInterchange Context triple: [Embankment station, isCentralLondonInterchange, true]
-
A.
isInInnerLondon
Indicates that one location lies within the administrative area defined as Inner London.
-
B.
isCityCentreStop
chosen
Indicates that a stop is located within or serves the central area of a city.
-
C.
servesCentralLondon
Indicates that something provides service or access specifically to the Central London area.
-
D.
isAdjacentStationOnJubileeLine
Indicates that two stations are directly next to each other as consecutive stops on the Jubilee Line.
-
E.
isAdjacentStationOnPiccadillyLine
Indicates that two stations are directly next to each other as consecutive stops on the Piccadilly 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:59 p.m.