Triple
T2966822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Kensington tube station |
E80185
|
entity |
| Predicate | fareZoneBoundary |
P844
|
FINISHED |
| Object | inner London |
—
|
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: inner London | Statement: [South Kensington tube station, fareZoneBoundary, inner London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneBoundary Context triple: [South Kensington tube station, fareZoneBoundary, inner London]
-
A.
hasFareZone
chosen
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
B.
boundaryName
Indicates the designated name or label assigned to a specific boundary or border between entities.
-
C.
fareControlLocation
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
D.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996e93788190ba9883714d4dfa0c |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.