Triple

T8855832
Position Surface form Disambiguated ID Type / Status
Subject EU Council Joint Action 2008/736/CFSP E210753 entity
Predicate createsMission P85003 FINISHED
Object EUMM Georgia chain of command and structure 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: EUMM Georgia chain of command and structure | Statement: [EU Council Joint Action 2008/736/CFSP, createsMission, EUMM Georgia chain of command and structure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: createsMission
Context triple: [EU Council Joint Action 2008/736/CFSP, createsMission, EUMM Georgia chain of command and structure]
  • A. publicMission
    Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
  • B. missionStart
    Indicates the point in time or event at which a mission or task officially begins.
  • C. exampleMission
    Indicates that one entity serves as a representative or illustrative mission associated with another entity.
  • D. missionDesign
    Indicates the relationship in which an entity plans, structures, and specifies the objectives, constraints, and procedures for carrying out a mission.
  • E. missionPlanning
    Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
  • 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_69ca838a424c8190b1ecac115c2927e7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60c7f51881909c847989f31f203a completed April 1, 2026, 12:03 a.m.
PD Predicate disambiguation batch_69cc5c25b874819084c9ba391703e066 completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5cffe8ec819084c12770fe0578f2 completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 6:50 p.m.