Triple
T32109170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Information Dominance Corps |
E820070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military information warfare community |
C22899
|
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 information warfare community Context triple: [Information Dominance Corps, instanceOf, military information warfare community]
-
A.
information warfare organization
chosen
An information warfare organization is an entity structured to plan, conduct, and coordinate operations that manipulate, protect, or exploit information and information systems to achieve strategic, operational, or tactical objectives.
-
B.
military planning community
The military planning community is the collective body of defense professionals, analysts, and decision-makers who develop, coordinate, and evaluate strategies, plans, and policies to achieve national security and military objectives.
-
C.
military community
A military community is a social group composed of service members, their families, veterans, and supporting personnel who share common experiences, resources, and culture related to military life.
-
D.
information systems command
An information systems command is a centralized authority responsible for directing, coordinating, and managing an organization’s information technology infrastructure, cybersecurity, and data operations to support mission objectives.
-
E.
cyberspace operations command
A cyberspace operations command is a military or governmental organizational entity responsible for planning, directing, and executing offensive, defensive, and support activities within and through cyberspace to achieve strategic and operational 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:27 a.m.