Triple

T30308929
Position Surface form Disambiguated ID Type / Status
Subject Council Decision 2019/408/CFSP E770867 entity
Predicate updatesMeasuresLaidDownIn P169069 FINISHED
Object Council Decision 2014/219/CFSP NE NERFINISHED

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: Council Decision 2014/219/CFSP | Statement: [Council Decision 2019/408/CFSP, updatesMeasuresLaidDownIn, Council Decision 2014/219/CFSP]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: updatesMeasuresLaidDownIn
Context triple: [Council Decision 2019/408/CFSP, updatesMeasuresLaidDownIn, Council Decision 2014/219/CFSP]
  • A. updated
    Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
  • B. updatedIn
    Indicates that an entity has undergone a change or modification within a specified time period or version context.
  • C. updatedEvery
    Indicates that something is refreshed or brought up to date at a regular, specified interval.
  • D. adoptedMeasure
    Indicates that an entity has formally accepted and put into effect a specific measure, policy, or course of action.
  • E. enactsMeasuresFrom
    Indicates that one entity implements or puts into effect measures, policies, or actions that originate from another entity or source.
  • 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_69f22488f224819081b0f3ec41ab975c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6816a2f348190b35b187ddb71c3a5 completed May 2, 2026, 10:57 p.m.
PD Predicate disambiguation batch_69f6760216108190bbb708d53a6c2c25 completed May 2, 2026, 10:09 p.m.
PDg Predicate description generation batch_69f676c35f3481909b9ba18a5662d6ce completed May 2, 2026, 10:12 p.m.
Created at: April 29, 2026, 7:50 p.m.