Triple
T10259764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Nations minority treaties |
E240564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international treaty regime |
C3194
|
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 treaty regime Context triple: [League of Nations minority treaties, instanceOf, international treaty regime]
-
A.
international legal regime
chosen
An international legal regime is a structured set of principles, norms, rules, and decision-making procedures agreed upon by states and other actors to govern behavior and cooperation in a specific issue-area of international relations.
-
B.
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.
-
C.
international legal mechanism
An international legal mechanism is a formal process, institution, or instrument established by states or international organizations to create, interpret, enforce, or resolve disputes about obligations under international law.
-
D.
international framework
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
-
E.
system of international law
A system of international law is a structured set of principles, rules, and institutions that govern the rights, duties, and interactions of states and other international actors in their relations with one another.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:32 a.m.