Triple
T8915139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Deployable Corps headquarters |
E212277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-readiness headquarters |
C25291
|
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: high-readiness headquarters Context triple: [NATO Deployable Corps headquarters, instanceOf, high-readiness headquarters]
-
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.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
C.
U.S. Army center of excellence
A U.S. Army center of excellence is an institutional organization that develops, integrates, and advances specialized doctrine, training, capabilities, and expertise for a specific warfighting or functional area across the Army.
-
D.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
E.
major command echelon
A major command echelon is a high-level organizational tier within a military or large institution that oversees multiple subordinate units and directs strategic operations, resources, and policies across a broad mission area.
- F. None of above. chosen
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.