Triple
T14691984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Councilman |
E345056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | position within the City of London Corporation |
C30775
|
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: position within the City of London Corporation Context triple: [Common Councilman, instanceOf, position within the City of London Corporation]
-
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.
ward of the City of London
A ward of the City of London is a historic administrative and electoral subdivision of the City, each with its own boundaries, governance structures, and representation in the City’s civic institutions.
-
C.
London alderman
chosen
A London alderman is a senior elected official of the City of London Corporation who represents a ward, participates in civic governance, and helps oversee the administration and ceremonial functions of the historic financial district.
-
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.
Lord Mayor
The Lord Mayor is the ceremonial head and often the public representative of a major city’s municipal government, typically presiding over civic functions and promoting the city’s interests.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.