Triple
T9747986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Portland Street Underground station |
E236364
|
entity |
| Predicate | isInCentralLondon |
P48857
|
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: [Great Portland Street Underground station, isInCentralLondon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCentralLondon Context triple: [Great Portland Street Underground station, isInCentralLondon, true]
-
A.
isInInnerLondon
Indicates that one location lies within the administrative area defined as Inner London.
-
B.
servesCentralLondon
chosen
Indicates that something provides service or access specifically to the Central London area.
-
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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f68f8b88190b44babf5ae17dfef |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.