Triple
T34715762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Nations sanctions on Italy |
E1000767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic sanctions |
C23186
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: diplomatic sanctions Context triple: [League of Nations sanctions on Italy, instanceOf, diplomatic sanctions]
-
A.
sanctions regime
chosen
A sanctions regime is a structured set of legal and policy measures—such as trade restrictions, asset freezes, and travel bans—imposed by one or more actors to coerce, deter, or punish targeted states, entities, or individuals.
-
B.
diplomatic policy
Diplomatic policy is a strategic framework guiding a state’s interactions and negotiations with other international actors to advance its political, economic, and security interests while managing conflicts and alliances.
-
C.
diplomatic relations
Diplomatic relations are the formal and informal interactions and agreements between sovereign states or international actors aimed at managing conflicts, fostering cooperation, and advancing mutual interests through negotiation and representation.
-
D.
trade embargo
A trade embargo is a government-imposed restriction that partially or completely prohibits commercial exchange of goods and services with a specific country, group, or entity for political, economic, or security reasons.
-
E.
diplomatic issue
A diplomatic issue is a matter of contention or concern between states or international actors that requires negotiation, communication, or policy decisions to manage or resolve.
- F. None of above.
Provenance (1 batch)
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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.