Triple
T10430953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Turkish Agreement of 1 December 1926 |
E245910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interwar 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: interwar treaty Context triple: [Greco-Turkish Agreement of 1 December 1926, instanceOf, interwar 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.
World War I–era diplomatic agreement
A World War I–era diplomatic agreement is a formal treaty, pact, or understanding negotiated between states during or immediately surrounding the First World War, aimed at managing alliances, territorial claims, military commitments, or postwar settlements.
-
C.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
D.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:13 p.m.