Triple
T34548397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampshire local authorities network |
E886995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional governance network |
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: regional governance network Context triple: [Hampshire local authorities network, instanceOf, regional governance network]
-
A.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
B.
regional institutional system
A regional institutional system is a coordinated network of organizations, rules, and practices within a specific geographic area that collectively shape governance, economic activity, and social outcomes.
-
C.
regional governance principle
A regional governance principle is a guiding norm or rule that shapes how political, economic, and social authority is organized, shared, and exercised across multiple jurisdictions within a specific geographic region.
-
D.
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.
-
E.
regional polity
A regional polity is a political entity or governing body that exercises authority and administration over a specific geographic region within or across states.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.