Triple
T5028206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaffing and winnowing |
E113228
|
entity |
| Predicate | senderAction |
P60609
|
FINISHED |
| Object | insert bogus packets with invalid MACs |
—
|
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: insert bogus packets with invalid MACs | Statement: [Chaffing and winnowing, senderAction, insert bogus packets with invalid MACs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: senderAction Context triple: [Chaffing and winnowing, senderAction, insert bogus packets with invalid MACs]
-
A.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
B.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
C.
sentMissionTo
Indicates that one entity dispatched or assigned another entity to carry out a specific mission at a particular destination or context.
-
D.
sendingState
Indicates the state that initiates or dispatches something (such as a person, document, or request) to another state or entity.
-
E.
sentOnMissionBy
Indicates that one entity was assigned or dispatched on a mission by another entity.
- F. None of above. chosen
Provenance (4 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738d852c8190a122354f1e1f5343 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.