Triple
T1837385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUNAVFOR MED IRINI |
E41094
|
entity |
| Predicate | participatingEntityType |
P6384
|
FINISHED |
| Object | EU member states armed forces |
—
|
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: EU member states armed forces | Statement: [EUNAVFOR MED IRINI, participatingEntityType, EU member states armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatingEntityType Context triple: [EUNAVFOR MED IRINI, participatingEntityType, EU member states armed forces]
-
A.
documentedEntityType
Indicates that an entity has been documented as belonging to a specific type or category.
-
B.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
C.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
D.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
E.
hasPartnershipType
Indicates the specific kind or category of partnership relationship that exists between entities.
- 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.