Triple

T9973110
Position Surface form Disambiguated ID Type / Status
Subject Anacostia Watershed Restoration Partnership E196257 entity
Predicate instanceOf P0 FINISHED
Object multi-jurisdictional collaboration 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: multi-jurisdictional collaboration
Context triple: [Anacostia Watershed Restoration Partnership, instanceOf, multi-jurisdictional collaboration]
  • A. 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.
  • B. intergovernmental partnership
    An intergovernmental partnership is a collaborative arrangement in which two or more governments coordinate policies, resources, and actions to address shared issues or achieve common goals.
  • C. 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.
  • D. judicial cooperation liaison unit
    A judicial cooperation liaison unit is a specialized body that facilitates communication, coordination, and mutual legal assistance between national and international judicial authorities to support cross-border investigations and prosecutions.
  • E. international agreement implementation area
    The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
  • 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_69ca82eea2b88190a0e511d21a31f386 completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 8:48 p.m.