Triple
T8914833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multinational Corps Northeast |
E212270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational corps headquarters |
C17522
|
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: multinational corps headquarters Context triple: [Multinational Corps Northeast, instanceOf, multinational corps headquarters]
-
A.
NATO rapid reaction corps headquarters
chosen
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.
multinational military forum
A multinational military forum is an organized platform where representatives from multiple countries' armed forces convene to discuss security issues, coordinate policies, share best practices, and enhance mutual understanding and cooperation.
-
C.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
D.
multinational airborne army formation
A multinational airborne army formation is a coordinated military unit composed of airborne-capable forces from multiple nations, trained and organized to conduct joint air-delivered operations under a unified command structure.
-
E.
corps artillery headquarters
A corps artillery headquarters is the command element responsible for planning, coordinating, and controlling all artillery and fire support operations within a military corps.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.