Triple
T27918825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC-West |
E706146
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO regional command |
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 regional command Context triple: [RC-West, instanceOf, NATO regional command]
-
A.
U.S.-led security assistance command
A U.S.-led security assistance command is a military organization responsible for planning, coordinating, and overseeing the provision of training, equipment, advisory support, and other security-related assistance to partner and allied nations.
-
B.
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.
-
C.
NATO administrative division
A NATO administrative division is an organizational unit within the North Atlantic Treaty Organization responsible for managing specific functions, regions, or operational domains to support the alliance’s political, military, and logistical activities.
-
D.
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.
-
E.
Geographic combatant command
A geographic combatant command is a unified military command responsible for planning and conducting operations within a specific, defined region of the world.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:55 p.m.