Triple
T29380952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Rapid Deployable Corps – Turkey |
E745133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-readiness force 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 force headquarters Context triple: [NATO Rapid Deployable Corps – Turkey, instanceOf, high-readiness force headquarters]
-
A.
high-readiness headquarters
chosen
A high-readiness headquarters is a command center designed, staffed, and equipped to rapidly assume control of operations, coordinate resources, and make timely decisions in response to emerging crises or missions.
-
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.
deployable corps-level headquarters
A deployable corps-level headquarters is a mobile, command-and-control organization capable of planning, coordinating, and directing large-scale, multi-division military operations across a theater of operations.
-
D.
National Defense Management Center
The National Defense Management Center is a centralized command and control facility responsible for coordinating, monitoring, and directing a nation's military and defense operations at the strategic level.
-
E.
headquarters and service regiment
A headquarters and service regiment is a military unit that provides command, control, and essential administrative and logistical support functions for a larger formation or group of subordinate units.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:35 p.m.