Triple
T1837377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUNAVFOR MED IRINI |
E41094
|
entity |
| Predicate | typeOfEmbargoMonitored |
P9979
|
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: [EUNAVFOR MED IRINI, typeOfEmbargoMonitored, arms embargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEmbargoMonitored Context triple: [EUNAVFOR MED IRINI, typeOfEmbargoMonitored, arms embargo]
-
A.
monitoredFor
chosen
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
B.
isWithheldBy
Indicates that something (such as information, resources, or permission) is deliberately not given, released, or made available by a particular entity.
-
C.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
D.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.