Triple

T8328989
Position Surface form Disambiguated ID Type / Status
Subject Council Directive 2001/86/EC E195027 entity
Predicate typeOfInvolvement P82125 FINISHED
Object information 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: information | Statement: [Council Directive 2001/86/EC, typeOfInvolvement, information]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfInvolvement
Context triple: [Council Directive 2001/86/EC, typeOfInvolvement, information]
  • A. mayBeInvolvedIn
    Indicates that an entity has a possible, but not certain, participation or role in a particular event, activity, or situation.
  • B. hasBeenInvolvedIn
    Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
  • C. oftenInvolvedWith
    Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
  • D. stillInvolvedIn
    Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
  • E. involves
    Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
  • 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_69ca82e87f2c8190bdb71ee29dfc642d completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fb812508190aed8a283dacf712e completed March 31, 2026, 8:03 a.m.
PD Predicate disambiguation batch_69cb70c3231c81909e3d463192c9de22 completed March 31, 2026, 6:59 a.m.
PDg Predicate description generation batch_69cb76d823b08190a54fadb50660cda5 completed March 31, 2026, 7:25 a.m.
Created at: March 30, 2026, 5:56 p.m.