Triple
T18619227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parties to the Paris Agreement |
E455106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | participant in international agreement |
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: participant in international agreement Context triple: [Parties to the Paris Agreement, instanceOf, participant in international agreement]
-
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.
participants in international initiative
Individuals, organizations, or states that actively engage in and contribute resources, expertise, or decision-making to a coordinated effort addressing issues of shared international concern.
-
C.
intergovernmental organization participant
An intergovernmental organization participant is an entity, typically a sovereign state or recognized international body, that formally takes part in the activities, decision-making processes, and governance structures of an intergovernmental organization.
-
D.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.