Triple
T15001802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Nicety |
E374108
|
entity |
| Predicate | typeOfDeception |
P116306
|
FINISHED |
| Object | operational deception |
—
|
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: operational deception | Statement: [Operation Nicety, typeOfDeception, operational deception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDeception Context triple: [Operation Nicety, typeOfDeception, operational deception]
-
A.
threatensDeceptionOf
Indicates that one entity poses or communicates a risk of deceiving or misleading another entity.
-
B.
decoyType
Indicates that one entity functions as a decoy and specifies the type or category of that decoy in relation to another entity or context.
-
C.
tricked
Indicates that one entity intentionally deceived another into believing something false or acting under a false impression.
-
D.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
E.
concealmentType
Indicates the specific manner or method by which something is hidden, obscured, or kept from detection.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded72fec948190b1c9705538c57976 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:54 a.m.