Triple
T9109641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Convention against Corruption |
E218563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international anti-corruption treaty |
C566
|
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: international anti-corruption treaty Context triple: [United Nations Convention against Corruption, instanceOf, international anti-corruption treaty]
-
A.
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.
-
B.
anti-corruption instrument
An anti-corruption instrument is a policy, mechanism, or tool designed to prevent, detect, and sanction corrupt practices within public or private institutions.
-
C.
treaty
chosen
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.
-
D.
corpus of international treaties
A corpus of international treaties is a structured collection of formal, legally binding agreements between sovereign states and/or international organizations, organized for analysis, reference, and comparative study.
-
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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:16 p.m.