Triple
T3091658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notting Hill Gate Underground station |
E64494
|
entity |
| Predicate | isInInnerLondon |
P45859
|
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: [Notting Hill Gate Underground station, isInInnerLondon, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInInnerLondon Context triple: [Notting Hill Gate Underground station, isInInnerLondon, yes]
-
A.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
-
B.
isMetropolitanBorough
Indicates that an entity functions as a metropolitan borough, i.e., a local government district within a large urban area that has borough status.
-
C.
containsMetropolitanBorough
Indicates that an administrative area includes within its boundaries one or more metropolitan boroughs as subordinate units.
-
D.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
E.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20eeee88190a5eecfce10e3848c |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.