Triple
T32753701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decision (CFSP) 2020/472 |
E837561
|
entity |
| Predicate | establishesMissionDomain |
P185975
|
FINISHED |
| Object | naval operation |
—
|
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: naval operation | Statement: [Council Decision (CFSP) 2020/472, establishesMissionDomain, naval operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesMissionDomain Context triple: [Council Decision (CFSP) 2020/472, establishesMissionDomain, naval operation]
-
A.
establishedMissionFor
Indicates that an entity formally created or set up a specific mission, assigning it purpose or objectives.
-
B.
missionTypeEstablished
Indicates that a specific type or category of mission has been formally defined and put into effect.
-
C.
describesMissionOf
Indicates that one entity specifies, explains, or defines the mission or purpose of another entity.
-
D.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
missionScope
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
- F. None of above. chosen
Provenance (4 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:12 a.m.