Triple
T25609574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellingcat |
E642010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source intelligence collective |
C50531
|
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: open-source intelligence collective Context triple: [Bellingcat, instanceOf, open-source intelligence collective]
-
A.
Internet Security Research Group
The Internet Security Research Group is a nonprofit organization dedicated to improving internet security by promoting and providing accessible, open, and automated security technologies and practices.
-
B.
signals intelligence tool
A signals intelligence tool is a system that intercepts, processes, and analyzes electronic signals and communications to extract actionable information and insights.
-
C.
signals intelligence alliance
A signals intelligence alliance is a cooperative partnership between nations or organizations to collect, share, and analyze electronic communications and signals data for security, defense, and strategic purposes.
-
D.
intelligence community
The intelligence community is a collective network of government agencies and organizations responsible for gathering, analyzing, and disseminating information to support national security and foreign policy decision-making.
-
E.
government affairs intelligence platform
A government affairs intelligence platform is a system that aggregates, analyzes, and visualizes legislative, regulatory, and political data to help organizations monitor policy developments and inform advocacy strategies.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:40 p.m.