Triple
T29338776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Covenants |
E743980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | category of multilateral treaties |
C13347
|
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: category of multilateral treaties Context triple: [International Covenants, instanceOf, category of multilateral treaties]
-
A.
corpus of international treaties
chosen
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.
-
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.
treaty practice
Treaty practice is the body of procedures, behaviors, and interpretive approaches that states and international actors consistently follow in negotiating, applying, and understanding treaties.
-
D.
private international law instrument
A private international law instrument is a legal tool—such as a treaty, regulation, or convention—that coordinates which jurisdiction’s laws and courts apply to cross-border private disputes and how foreign judgments are recognized and enforced.
-
E.
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.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:32 p.m.