Triple
T22488159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onion services |
E555944
|
entity |
| Predicate | threatModelIncludes |
P132137
|
FINISHED |
| Object | network surveillance |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: network surveillance | Statement: [Onion services, threatModelIncludes, network surveillance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatModelIncludes Context triple: [Onion services, threatModelIncludes, network surveillance]
-
A.
hasThreatModel
chosen
Indicates that an entity is associated with a specific threat model describing potential risks, adversaries, and attack scenarios relevant to it.
-
B.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
C.
threatStatusSystem
Indicates the classification framework or system used to assign a conservation or threat status to an entity.
-
D.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
E.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
- F. None of above.
Provenance (3 batches)
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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3e73108190be5ca89ea96a85e4 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.