Triple
T20947075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hackney South and Shoreditch |
E515869
|
entity |
| Predicate | hasInnerLondonStatus |
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: [Hackney South and Shoreditch, hasInnerLondonStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerLondonStatus Context triple: [Hackney South and Shoreditch, hasInnerLondonStatus, yes]
-
A.
isInInnerLondon
chosen
Indicates that one location lies within the administrative area defined as Inner London.
-
B.
hasOuterLondonBorough
Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
-
C.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
-
D.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
-
E.
hasInnerCity
Indicates that one entity contains or is associated with a specific inner city within its boundaries or structure.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad97aa48190b4be692e3afce8c9 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:57 p.m.