Triple
T12114641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromley South railway station |
E288523
|
entity |
| Predicate | isInLondonTravelcardArea |
P75854
|
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: [Bromley South railway station, isInLondonTravelcardArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInLondonTravelcardArea Context triple: [Bromley South railway station, isInLondonTravelcardArea, yes]
-
A.
isWithinLondonFareSystem
chosen
Indicates that an entity (such as a station, stop, or route) is located inside the area covered by the London public transport fare system.
-
B.
isInInnerLondon
Indicates that one location lies within the administrative area defined as Inner London.
-
C.
hasOuterLondonBorough
Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
-
D.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
-
E.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.