Triple
T34302409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Syndicate |
E880216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rogue intelligence network |
C3529
|
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: rogue intelligence network Context triple: [the Syndicate, instanceOf, rogue intelligence network]
-
A.
regional intelligence formation
Regional intelligence formation is the process by which localized knowledge, data, and contextual insights are gathered, synthesized, and structured within a specific geographic or cultural area to support informed decision-making and strategic action.
-
B.
covert intelligence organization
chosen
A covert intelligence organization is a secretive entity that gathers, analyzes, and acts on sensitive information through clandestine methods to influence or protect national or organizational interests.
-
C.
underground network
An underground network is a covert, often informal system of interconnected individuals, groups, or infrastructure that operates out of public view to share resources, information, or influence.
-
D.
Intelligence Processing Unit
An Intelligence Processing Unit is a specialized computing component designed to efficiently execute and accelerate artificial intelligence and machine learning workloads through massively parallel, low-precision, and dataflow-oriented architectures.
-
E.
security and intelligence unit
A security and intelligence unit is an organized group responsible for gathering, analyzing, and acting on information to prevent threats and protect people, assets, and critical operations.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.