Triple
T20198289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Combat Mission Teams |
E493145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military cyber operations unit |
C41697
|
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 cyber operations unit Context triple: [Army Combat Mission Teams, instanceOf, military cyber operations unit]
-
A.
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.
-
B.
cyberspace operations component
chosen
A cyberspace operations component is an organizational element responsible for planning, directing, and executing military or security activities within and through cyberspace to achieve assigned objectives.
-
C.
military operations center
A military operations center is a centralized facility where commanders and staff monitor, coordinate, and direct military activities and resources in real time.
-
D.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
E.
operational unit
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.