Triple
T9648246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-2 ICBM |
E233262
|
entity |
| Predicate | threatTarget |
P1358
|
FINISHED |
| Object | strategic targets in the United States |
—
|
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: strategic targets in the United States | Statement: [RT-2 ICBM, threatTarget, strategic targets in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatTarget Context triple: [RT-2 ICBM, threatTarget, strategic targets in the United States]
-
A.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
B.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
C.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
D.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
E.
threat
chosen
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bac55b48190ab2a8f9bb83c951e |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.