Triple
T6290754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NNSC |
E141009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armistice supervisory commission |
C5969
|
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: armistice supervisory commission Context triple: [NNSC, instanceOf, armistice supervisory commission]
-
A.
armistice supervision body
chosen
An armistice supervision body is an organization established to monitor, verify, and enforce compliance with the terms of a ceasefire or armistice agreement between conflicting parties.
-
B.
World War I armistice
The World War I armistice is the formal agreement signed on November 11, 1918, between the Allies and Germany that ended the fighting on the Western Front and effectively brought World War I to a close pending a final peace treaty.
-
C.
peace commission
A peace commission is an official body established to investigate conflicts, promote dialogue, and recommend measures to prevent, resolve, or reconcile disputes between parties.
-
D.
conciliation commission
A conciliation commission is a temporary, impartial body established—often under international or contractual agreements—to investigate a dispute and propose nonbinding solutions aimed at amicable settlement between the parties.
-
E.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:27 p.m.