Triple
T29362439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contracting Parties to the International Treaty on Plant Genetic Resources for Food and Agriculture |
E744626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty party collective |
C7269
|
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: treaty party collective Context triple: [Contracting Parties to the International Treaty on Plant Genetic Resources for Food and Agriculture, instanceOf, treaty party collective]
-
A.
party to an international treaty
chosen
A party to an international treaty is a state or international organization that has formally consented to be bound by the treaty’s terms in accordance with international law.
-
B.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
D.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
E.
group of national governments
A group of national governments is a collective of sovereign state authorities that coordinate policies, decisions, or actions on shared interests or issues.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:19 p.m.