Triple
T3447274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park Corner Underground station |
E72706
|
entity |
| Predicate | servesCentralLondon |
P48857
|
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: [Hyde Park Corner Underground station, servesCentralLondon, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCentralLondon Context triple: [Hyde Park Corner Underground station, servesCentralLondon, yes]
-
A.
isInInnerLondon
Indicates that one location lies within the administrative area defined as Inner London.
-
B.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
-
C.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
-
D.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
E.
hasOuterLondonBorough
Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba6efb188190b989fa4d6f28e16b |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:16 p.m.