Triple
T10086843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multinational Corps Southeast |
E215243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land forces headquarters |
C25290
|
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: land forces headquarters Context triple: [Multinational Corps Southeast, instanceOf, land forces headquarters]
-
A.
component of land forces
A component of land forces is an organized, functionally distinct element of an army’s ground combat structure, such as infantry, armor, artillery, or support units, that contributes specific capabilities to land operations.
-
B.
land warfare service branch
A land warfare service branch is a military organization primarily responsible for conducting combat and support operations on land using ground forces and associated assets.
-
C.
deployable corps-level headquarters
chosen
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.
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.
regional land command
A regional land command is a military organizational structure responsible for planning, directing, and coordinating all land-based operations and forces within a defined geographic area.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 9:01 p.m.