Triple
T29384768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 2009 |
E745220
|
entity |
| Predicate | typeOfSanctionsAffected |
P18137
|
FINISHED |
| Object | arms embargo |
—
|
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: arms embargo | Statement: [United Nations Security Council Resolution 2009, typeOfSanctionsAffected, arms embargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSanctionsAffected Context triple: [United Nations Security Council Resolution 2009, typeOfSanctionsAffected, arms embargo]
-
A.
typeOfSanction
chosen
Indicates the specific category or kind of sanction that is applied in a given situation.
-
B.
appliedSanctionsTo
Indicates that one entity has imposed sanctions or punitive restrictions on another entity.
-
C.
typeOfSanctionsAuthority
Indicates the authority or legal basis under which specific sanctions are imposed or administered.
-
D.
countrySubjectToSanctions
Indicates that a country is currently facing formal sanctions or restrictive measures imposed by another state or international body.
-
E.
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.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 28, 2026, 2:37 p.m.