Triple
T8729852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUNAVFOR MED Operation Sophia |
E207223
|
entity |
| Predicate | typeOfEmbargoEnforcement |
P72685
|
FINISHED |
| Object | UN arms embargo on Libya |
—
|
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: UN arms embargo on Libya | Statement: [EUNAVFOR MED Operation Sophia, typeOfEmbargoEnforcement, UN arms embargo on Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEmbargoEnforcement Context triple: [EUNAVFOR MED Operation Sophia, typeOfEmbargoEnforcement, UN arms embargo on Libya]
-
A.
embargoStartDate
Indicates the date on which an embargo or restriction on access, release, or distribution begins to take effect.
-
B.
embargoTarget
chosen
Indicates that one entity is the object or subject of an embargo imposed by another entity.
-
C.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
D.
restraintType
Indicates the specific kind or method of restraint applied in a given situation or relationship.
-
E.
detainedUntil
Indicates that an entity is held in custody or confinement up to a specified time or until a particular condition is met.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d26d280819085e15d4917c2b9a5 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.