Triple
T22488211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluggable transports |
E555945
|
entity |
| Predicate | aimsToDefeat |
P47072
|
FINISHED |
| Object | deep packet inspection |
—
|
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: deep packet inspection | Statement: [Pluggable transports, aimsToDefeat, deep packet inspection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToDefeat Context triple: [Pluggable transports, aimsToDefeat, deep packet inspection]
-
A.
aimsToEliminate
Indicates an intention or directed effort by one entity to remove, destroy, or completely get rid of another entity or condition.
-
B.
designedToDefeat
chosen
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
C.
aimsToCapture
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
D.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
E.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary 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.