Triple
T19821146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter-Allied military commission |
E476196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international military commission |
C438
|
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 military commission Context triple: [Inter-Allied military commission, instanceOf, international military commission]
-
A.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
-
B.
military tribunal
chosen
A military tribunal is a specialized court convened by the armed forces to try members of the military or, in some cases, civilians, for violations of military law or the laws of war.
-
C.
international claims commission
An international claims commission is a temporary or permanent body established by states or international organizations to adjudicate and resolve financial or property claims arising from disputes, conflicts, or treaty violations across national borders.
-
D.
international criminal tribunal statute
An international criminal tribunal statute is a foundational legal instrument that establishes the jurisdiction, structure, procedures, and substantive crimes for a tribunal tasked with prosecuting individuals for serious violations of international law.
-
E.
inter-Allied military staff
A collaborative body of military officers from multiple allied nations responsible for joint strategic planning, coordination, and command of combined armed forces.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.