Triple
T978807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Headquarters Allied Powers Europe |
E21119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO military 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: NATO military headquarters Context triple: [Supreme Headquarters Allied Powers Europe, instanceOf, NATO military headquarters]
-
A.
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.
-
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.
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.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:40 p.m.