Triple

T8882075
Position Surface form Disambiguated ID Type / Status
Subject Council Decision 2014/219/CFSP E211434 entity
Predicate OJCitationPage P65929 FINISHED
Object 21 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: 21 | Statement: [Council Decision 2014/219/CFSP, OJCitationPage, 21]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: OJCitationPage
Context triple: [Council Decision 2014/219/CFSP, OJCitationPage, 21]
  • A. legalCitationSystem
    Indicates a system or convention used to reference and identify legal authorities such as cases, statutes, or regulations.
  • B. legalCitation
    Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
  • C. legalCitationNumber chosen
    Indicates the specific identifying number assigned to a legal citation that references a law, case, or legal document.
  • D. formerLegalCitation
    Indicates that one legal citation previously referred to or governed a matter but has since been replaced, superseded, or is no longer the current controlling citation.
  • E. legalCitationForm
    Indicates the standardized way in which a legal authority (such as a case, statute, or regulation) should be cited in legal documents.
  • 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_69ca838f9e20819096ab1f236a70381a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc616a01f48190b8bbde0e898a38c7 completed April 1, 2026, 12:06 a.m.
PD Predicate disambiguation batch_69cc5c2956788190a311c647b4da17a6 completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:53 p.m.