Triple
T29941549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwaii Haanas Agreement |
E760511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | co-management agreement |
C32723
|
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: co-management agreement Context triple: [Gwaii Haanas Agreement, instanceOf, co-management agreement]
-
A.
joint management arrangement
chosen
A joint management arrangement is a structured agreement in which two or more parties share authority, responsibilities, and decision-making over a specific resource, project, or organization.
-
B.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
C.
management partnership
A management partnership is a collaborative arrangement in which two or more parties jointly oversee, coordinate, and make strategic decisions for shared resources, projects, or organizations to achieve mutually agreed objectives.
-
D.
managing agency
A managing agency is an organization or entity responsible for overseeing, coordinating, and administering the operations, resources, and strategic direction of a project, program, or group on behalf of its stakeholders or owners.
-
E.
defense cost-sharing agreement
A defense cost-sharing agreement is a contractual arrangement in which two or more parties agree to allocate and reimburse expenses related to legal defense in connection with specified claims or proceedings.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:22 p.m.