Triple
T12923811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLA cyber forces |
E309190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military cyber warfare unit |
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 cyber warfare unit Context triple: [PLA cyber forces, instanceOf, military cyber warfare unit]
-
A.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
C.
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.
-
D.
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.
-
E.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:42 p.m.