Triple
T33930920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Command A, 4th Armored Division |
E869887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical headquarters |
C400
|
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: tactical headquarters Context triple: [Combat Command A, 4th Armored Division, instanceOf, tactical headquarters]
-
A.
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.
-
B.
high-readiness headquarters
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.
-
C.
headquarters
chosen
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
D.
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.
-
E.
military operations center
A military operations center is a centralized facility where commanders and staff monitor, coordinate, and direct military activities and resources in real time.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.