Triple
T27938182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Board of Works |
E700668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metropolitan government body |
C16436
|
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: metropolitan government body Context triple: [Metropolitan Board of Works, instanceOf, metropolitan government body]
-
A.
metropolitan authority
chosen
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.
-
B.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
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.
autonomous city government
An autonomous city government is a self-governing municipal authority that exercises significant political, administrative, and fiscal control over local affairs independent of higher levels of government.
-
E.
centrally governed city
A centrally governed city is an urban area whose key administrative, economic, and policy decisions are directed and controlled by a single, central authority rather than by multiple local or decentralized bodies.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 7:15 p.m.