Triple
T5199982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emilio Largo |
E117368
|
entity |
| Predicate | methodOfExtortion |
P859
|
FINISHED |
| Object | theft and threat of detonation of nuclear warheads |
—
|
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: theft and threat of detonation of nuclear warheads | Statement: [Emilio Largo, methodOfExtortion, theft and threat of detonation of nuclear warheads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfExtortion Context triple: [Emilio Largo, methodOfExtortion, theft and threat of detonation of nuclear warheads]
-
A.
methodOfDisappearance
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
-
B.
diversionMethod
Indicates the method or tactic used to distract, mislead, or redirect attention or resources away from a primary target or activity.
-
C.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
E.
interrogationMethod
Indicates the technique or approach used by one party to question or extract information from 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.