Triple

T13537279
Position Surface form Disambiguated ID Type / Status
Subject EU directives E323292 entity
Predicate nonComplianceCanLeadTo P7914 FINISHED
Object infringement proceedings 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: infringement proceedings | Statement: [EU directives, nonComplianceCanLeadTo, infringement proceedings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nonComplianceCanLeadTo
Context triple: [EU directives, nonComplianceCanLeadTo, infringement proceedings]
  • A. riskIfNoncompliance chosen
    Indicates that a risk or negative consequence will occur if the specified rules, requirements, or obligations are not complied with.
  • B. legalStatusOfNoncompliance
    Indicates the legal characterization or consequences assigned to an instance of noncompliance with a rule, law, or obligation.
  • C. accusationsOfNonComplianceBy
    Indicates that one party has formally alleged that another party has failed to meet required rules, standards, or obligations.
  • D. violationConsequences
    Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
  • E. nonCooperationMayLeadTo
    Indicates that a lack of cooperation in a situation can potentially result in certain negative or consequential outcomes.
  • 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_69d8076776248190bdf0d4fa1f85a5fc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafbe39948190808062d4eff91841 completed April 12, 2026, 2:44 p.m.
PD Predicate disambiguation batch_69dbae1046c48190b4ee98c6c9cb9d85 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:45 p.m.