Triple
T24727467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall, Southwark |
E618192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former seat of the Greater London Authority |
C42939
|
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: former seat of the Greater London Authority Context triple: [City Hall, Southwark, instanceOf, former seat of the Greater London Authority]
-
A.
former metropolitan borough
A former metropolitan borough is a once-autonomous urban local government district that has been abolished or reorganized, typically through administrative restructuring or consolidation into a larger authority.
-
B.
former seat of local government
chosen
A former seat of local government is a building or location that previously served as the primary administrative center for a local governing authority but no longer holds that official function.
-
C.
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.
-
D.
district of London
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.
-
E.
metropolitan authority
A metropolitan authority is a governing body responsible for planning, coordinating, and managing public services and development across a large urban area and its surrounding municipalities.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
Created at: April 18, 2026, 4 a.m.