Triple
T19944195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korean economy |
E479380
|
entity |
| Predicate | sanctionsReasons |
P42046
|
FINISHED |
| Object | nuclear weapons program |
—
|
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: nuclear weapons program | Statement: [North Korean economy, sanctionsReasons, nuclear weapons program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctionsReasons Context triple: [North Korean economy, sanctionsReasons, nuclear weapons program]
-
A.
reasonForSanctions
chosen
Indicates the underlying cause or justification for imposing sanctions on an entity.
-
B.
coSanctions
Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
-
C.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
-
D.
relatedSanctions
Indicates that there is an association between an entity and one or more sanctions, such as penalties, restrictions, or punitive measures applied in connection with that entity.
-
E.
sanctionsMayInclude
Indicates that specified sanctions are permitted to contain or encompass certain listed measures, penalties, or restrictions.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a64b2788190a49c4ed40aa93b98 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.