Triple
T8914872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Support and Enabling Command |
E212271
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO headquarters |
C11966
|
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: NATO headquarters Context triple: [Joint Support and Enabling Command, instanceOf, NATO 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.
seat of a supranational parliament
The seat of a supranational parliament is the designated city or complex of buildings where the parliament’s official plenary sessions, administrative functions, and key institutional activities are formally conducted.
-
C.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
-
D.
NATO administrative division
chosen
A NATO administrative division is an organizational unit within the North Atlantic Treaty Organization responsible for managing specific functions, regions, or operational domains to support the alliance’s political, military, and logistical activities.
-
E.
seat of an international organization
A seat of an international organization is the city or specific location where the organization’s principal headquarters and core administrative functions are permanently established.
- 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.