Triple
T8915008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Air Operations Centres |
E212274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO command and control facility |
C9984
|
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: NATO command and control facility Context triple: [Combined Air Operations Centres, instanceOf, NATO command and control facility]
-
A.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
-
B.
NATO capability
A NATO capability is a specific military, political, or logistical asset, function, or competence that member states collectively develop, maintain, and coordinate to fulfill the Alliance’s strategic objectives and operational requirements.
-
C.
component of NATO command structure
chosen
A component of NATO command structure is an organizational entity—such as a headquarters, command, or specialized unit—responsible for planning, directing, and coordinating specific military or strategic functions within the Alliance’s integrated chain of command.
-
D.
Luftwaffe command position
A Luftwaffe command position is an organizational role within the German air force hierarchy responsible for directing air operations, managing resources, and implementing strategic and tactical decisions.
-
E.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.