Triple
T2363891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention on Cybercrime |
E47336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybercrime 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: cybercrime treaty Context triple: [Convention on Cybercrime, instanceOf, cybercrime treaty]
-
A.
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.
-
B.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
C.
party to an international treaty
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.
-
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.
counterterrorism law
Counterterrorism law is the body of domestic and international legal rules, procedures, and powers designed to prevent, investigate, and punish acts of terrorism while balancing national security with the protection of civil liberties and human rights.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:55 p.m.