Triple
T75774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GenocideConvention1948 |
E1514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | criminal law 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: criminal law treaty Context triple: [GenocideConvention1948, instanceOf, criminal law 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.
international criminal proceeding
An international criminal proceeding is a formal legal process conducted by an international or hybrid court to investigate, prosecute, and adjudicate individuals accused of serious crimes under international law, such as genocide, war crimes, and crimes against humanity.
-
C.
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.
-
D.
crimeAgainstHumanity
A crimeAgainstHumanity is a widespread or systematic attack directed against any civilian population, committed with knowledge of the attack, involving acts such as murder, enslavement, deportation, torture, or other inhumane conduct that severely violates fundamental human rights.
-
E.
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.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.