Triple
T17408517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Glimmer |
E423282
|
entity |
| Predicate | natureOfDeception |
P116306
|
FINISHED |
| Object | tactical-level diversion |
—
|
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: tactical-level diversion | Statement: [Operation Glimmer, natureOfDeception, tactical-level diversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfDeception Context triple: [Operation Glimmer, natureOfDeception, tactical-level diversion]
-
A.
typeOfDeception
chosen
Indicates the specific kind or category of deceptive act that one entity employs toward another or in a given context.
-
B.
threatensDeceptionOf
Indicates that one entity poses or communicates a risk of deceiving or misleading another entity.
-
C.
triesToRevealTruthTo
Indicates an attempt by one entity to make another entity aware of what it believes to be the true facts or reality of a situation.
-
D.
unawareOfTrueIdentityOf
Indicates that one entity does not know or recognize the real or actual identity of another entity.
-
E.
concealmentType
Indicates the specific manner or method by which something is hidden, obscured, or kept from detection.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b08d5a881909e7a5b2ae2c60898 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.