Triple
T6664710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Deal Board |
E151569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local partnership body |
C18021
|
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 partnership body Context triple: [Town Deal Board, instanceOf, local partnership body]
-
A.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
B.
local government association
A local government association is an organization that represents and supports the collective interests, coordination, and capacity-building of local authorities within a specific region or country.
-
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 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.
-
E.
multi-agency partnership
chosen
A multi-agency partnership is a collaborative arrangement in which multiple organizations from different sectors coordinate resources, expertise, and decision-making to achieve shared goals that no single agency could accomplish as effectively alone.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:02 p.m.