Triple

T29065262
Position Surface form Disambiguated ID Type / Status
Subject Nidderdale AONB Joint Advisory Committee E735656 entity
Predicate instanceOf P0 FINISHED
Object multi-agency partnership body C43914 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: multi-agency partnership body
Context triple: [Nidderdale AONB Joint Advisory Committee, instanceOf, multi-agency partnership body]
  • A. multi-agency partnership
    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.
  • B. partnership body chosen
    A partnership body is an organized group formed by two or more independent entities that collaborate under agreed arrangements to pursue shared goals, responsibilities, and benefits.
  • C. interagency group
    An interagency group is a collaborative body composed of representatives from multiple government agencies that coordinates policies, resources, and actions on shared issues or objectives.
  • D. community-based partnership
    A community-based partnership is a collaborative relationship between local organizations, residents, and stakeholders who share resources, decision-making, and responsibilities to address community needs and achieve mutually beneficial goals.
  • E. international partnership organization
    An international partnership organization is a collaborative entity formed by multiple countries, institutions, or stakeholders to coordinate resources, expertise, and policies toward shared global goals and initiatives.
  • 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_69f077e85498819088b65186550da8cd completed April 28, 2026, 9:03 a.m.
Created at: April 28, 2026, 10:17 a.m.