Triple
T32753711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decision (CFSP) 2020/472 |
E837561
|
entity |
| Predicate | operationNameMeaning |
P201873
|
FINISHED |
| Object | Greek word for peace |
—
|
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: Greek word for peace | Statement: [Council Decision (CFSP) 2020/472, operationNameMeaning, Greek word for peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationNameMeaning Context triple: [Council Decision (CFSP) 2020/472, operationNameMeaning, Greek word for peace]
-
A.
operationName
Indicates the specific action or procedure being performed or invoked within a process or system.
-
B.
operationCodeName
Indicates that an operation is associated with a specific code name used to identify or refer to it.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operation
Indicates that one entity performs, carries out, or controls the functioning of another entity or system.
-
E.
missionNameMeaning
Indicates that one entity specifies or explains the meaning or significance of the name of a mission associated with another entity.
- 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_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: May 1, 2026, 1:12 a.m.