Triple
T12678673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Rules for Demand Guarantees |
E302887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | set of international rules |
C12531
|
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: set of international rules Context triple: [Uniform Rules for Demand Guarantees, instanceOf, set of international rules]
-
A.
body of international legal norms
A body of international legal norms is the coherent set of binding and non-binding rules, principles, and standards that regulate relations and conduct among states and other international actors.
-
B.
set of legal provisions
chosen
A set of legal provisions is an organized collection of formally enacted rules or clauses that together define rights, obligations, procedures, and consequences within a specific legal framework or context.
-
C.
symbol of international law
A symbol of international law is a visual or conceptual representation, such as scales of justice, a gavel, or the UN emblem, that signifies the principles, institutions, and norms governing legal relations between states and other international actors.
-
D.
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.
-
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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:20 p.m.