Triple
T4223263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association of Greater Manchester Authorities |
E94391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-municipal organization |
C4331
|
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: inter-municipal organization Context triple: [Association of Greater Manchester Authorities, instanceOf, inter-municipal organization]
-
A.
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.
-
B.
collective municipality
A collective municipality is an administrative unit comprising several smaller municipalities that collaborate to share services and governance functions while retaining their individual local identities.
-
C.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
D.
inter-district collaborative
An inter-district collaborative is a structured partnership among multiple school districts that share resources, expertise, and decision-making to improve educational services and outcomes across their combined communities.
-
E.
regional organisation of councils
chosen
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.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:04 p.m.