Triple
T9406349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führerhauptquartier system |
E226597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network of military headquarters |
C1086
|
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: network of military headquarters Context triple: [Führerhauptquartier system, instanceOf, network of military headquarters]
-
A.
military structure
A military structure is an organized framework of ranks, units, and command relationships that defines how armed forces are arranged, governed, and coordinated to conduct operations.
-
B.
military administrative structure
A military administrative structure is the organized system of offices, roles, procedures, and chains of command that manage the planning, support, and governance of armed forces.
-
C.
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.
-
D.
military installation
chosen
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.
U.S. Department of Defense network
A U.S. Department of Defense network is a secure, government-operated information and communications infrastructure used to support military operations, intelligence, logistics, and administrative functions across classified and unclassified environments.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:47 p.m.