Triple
T16347754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Council in Paris |
E396977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-Allied commission |
C21444
|
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: inter-Allied commission Context triple: [Allied Council in Paris, instanceOf, inter-Allied commission]
-
A.
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.
-
B.
inter-Allied diplomatic body
chosen
An inter-Allied diplomatic body is a formal organization composed of representatives from multiple allied nations, established to coordinate joint policies, strategies, and negotiations in pursuit of shared political, military, or economic objectives.
-
C.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
D.
Verteidigungsausschuss
Der Verteidigungsausschuss ist ein parlamentarisches Gremium, das die Verteidigungs- und Sicherheitspolitik eines Staates überwacht, Gesetzentwürfe im Verteidigungsbereich berät und die Arbeit des Verteidigungsministeriums kontrolliert.
-
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.