Triple
T31561039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied air forces in World War I |
E805262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military alliance air forces |
C3997
|
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: military alliance air forces Context triple: [Allied air forces in World War I, instanceOf, military alliance air forces]
-
A.
Allied air force
chosen
Allied air force: The collective aerial military forces of nations united in a coalition, coordinating air operations to achieve shared strategic and tactical objectives in conflict.
-
B.
military alliance pattern
A military alliance pattern is a recurring strategic arrangement in which multiple states or actors coordinate defense commitments, resource sharing, and joint planning to deter threats and enhance collective security.
-
C.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
D.
multinational airborne army formation
A multinational airborne army formation is a coordinated military unit composed of airborne-capable forces from multiple nations, trained and organized to conduct joint air-delivered operations under a unified command structure.
-
E.
multinational military coalition
A multinational military coalition is a temporary or long-term alliance of armed forces from multiple sovereign states that coordinate resources, strategy, and operations to achieve shared security or defense objectives.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:15 p.m.