Triple

T2828962
Position Surface form Disambiguated ID Type / Status
Subject Education, Youth, Culture and Sport Council E54989 entity
Predicate mayDecideBy P9044 FINISHED
Object unanimity in specific areas 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: unanimity in specific areas | Statement: [Education, Youth, Culture and Sport Council, mayDecideBy, unanimity in specific areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayDecideBy
Context triple: [Education, Youth, Culture and Sport Council, mayDecideBy, unanimity in specific areas]
  • A. makesDecisionBy chosen
    Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
  • B. decidedWith
    Indicates that an entity made a decision jointly or in agreement with another entity.
  • C. decidesOn
    Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
  • D. decides
    Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
  • E. decisionsAre
    Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
  • 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_69ab49e100c0819082a40cb797383243 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde97168c8190b31122b2ad9fdebf completed March 7, 2026, 8:15 a.m.
PD Predicate disambiguation batch_69abdd0acab881909e8c25cbef83678c completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:59 p.m.