Triple
T847351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Trianon |
E18305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I peace 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: World War I peace treaty Context triple: [Treaty of Trianon, instanceOf, World War I peace treaty]
-
A.
League of Nations mandate
A League of Nations mandate was a legal and administrative arrangement by which a victorious World War I power governed a former German or Ottoman territory under international supervision, ostensibly until it was deemed ready for self-rule.
-
B.
League of Nations document
A League of Nations document is an official written record, report, treaty, resolution, or communication produced or authorized by the League of Nations in the course of its international governance and diplomatic activities.
-
C.
League of Nations body
A League of Nations body is an organizational unit or agency established under the League of Nations to carry out specific functions such as maintaining peace, overseeing mandates, resolving disputes, or coordinating international cooperation among member states.
-
D.
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.
-
E.
organ of the League of Nations
An organ of the League of Nations is an institutional body established by the League to perform specific functions such as decision-making, administration, or dispute resolution within the organization’s international governance framework.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.