Triple
T24788791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindenburg–Ludendorff command partnership |
E620191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military command partnership |
C8007
|
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: military command partnership Context triple: [Hindenburg–Ludendorff command partnership, instanceOf, military command partnership]
-
A.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
-
B.
civil-military coordination structure
A civil-military coordination structure is an organized framework that defines roles, processes, and communication channels between civilian authorities and military forces to plan, manage, and execute joint operations effectively and lawfully.
-
C.
joint command
chosen
A joint command is a unified military authority structure that coordinates and directs operations involving multiple service branches or allied forces to achieve common strategic objectives.
-
D.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
E.
military police command
A military police command is an organizational unit within the armed forces responsible for law enforcement, security operations, discipline, and order among military personnel and installations.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:46 a.m.