Triple
T953816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater London Authority |
E20581
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional government body |
C3213
|
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: regional government body Context triple: [Greater London Authority, instanceOf, regional government body]
-
A.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
B.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
C.
independent regional agency
An independent regional agency is an autonomous public or quasi-public organization that operates within a specific geographic region to plan, coordinate, and deliver specialized services or regulatory functions separate from direct control by central government bodies.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
public administration body
chosen
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.