Triple
T13534727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wards of the City of London |
E323231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of the City of London |
C4328
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: subdivision of the City of London Context triple: [Wards of the City of London, instanceOf, subdivision of the City of London]
-
A.
component of the City of London Corporation
A component of the City of London Corporation is any organizational unit, office, committee, or functional body that operates under its authority to manage municipal governance, services, and regulatory responsibilities within the City of London.
-
B.
district of London
chosen
A district of London is a defined urban area within the Greater London region, characterized by its own local identity, history, and mix of residential, commercial, and cultural features.
-
C.
small borough
A small borough is a minor administrative division, typically a compact urban or semi-urban community with limited population and local self-governance within a larger municipal or regional structure.
-
D.
sub-market of the London Stock Exchange
A sub-market of the London Stock Exchange is a distinct segment within the broader exchange that groups companies or securities based on specific criteria such as size, sector, regulatory requirements, or listing standards.
-
E.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
- F. None of above.
Provenance (1 batch)
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.