Triple
T10110224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Front system of the Chinese Communist Party |
E218220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | influence operation system |
C27427
|
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: influence operation system Context triple: [United Front system of the Chinese Communist Party, instanceOf, influence operation system]
-
A.
global operational system
A global operational system is an integrated framework of processes, technologies, and governance structures that coordinates and manages activities across international boundaries to ensure consistent, efficient, and reliable operations worldwide.
-
B.
multiuser operating system
A multiuser operating system is a software environment that allows multiple users to access and use a computer system's resources simultaneously and independently, typically through separate user accounts and sessions.
-
C.
operating system enhancement pack
An operating system enhancement pack is a collection of add-on tools, features, and optimizations designed to extend and improve the functionality, performance, and usability of an existing operating system.
-
D.
operating system family
An operating system family is a conceptual grouping of related operating systems that share a common architecture, design principles, and core components, often evolving from a shared codebase or lineage.
-
E.
systems operator
A systems operator is responsible for monitoring, controlling, and maintaining computer systems or infrastructure to ensure continuous, efficient, and secure operation.
- F. None of above. chosen
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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.