Triple
T22736023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor and Cabinet (London Borough of Newham) |
E562273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government executive |
C38758
|
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: local government executive Context triple: [Mayor and Cabinet (London Borough of Newham), instanceOf, local government executive]
-
A.
municipal government position
A municipal government position is a role within a city or local government responsible for administering public services, implementing local policies, and managing community resources and regulations.
-
B.
municipal government officeholders
chosen
Individuals elected or appointed to positions of authority within a city or local government, responsible for creating, implementing, and overseeing municipal policies, services, and regulations.
-
C.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
D.
municipal administration
Municipal administration is the organizational structure and processes through which a local government manages public services, implements policies, and oversees the day-to-day operations of a municipality.
-
E.
county government position
A county government position is a public office or role within a county’s administrative structure responsible for delivering local services, enforcing county policies, and representing the interests of county residents.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:22 p.m.