Triple

T35378439
Position Surface form Disambiguated ID Type / Status
Subject Tariefcommissie (Netherlands) E1022578 entity
Predicate referredToCourt P124421 FINISHED
Object Court of Justice of the European Union NE NERFINISHED

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: Court of Justice of the European Union | Statement: [Tariefcommissie (Netherlands), referredToCourt, Court of Justice of the European Union]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: referredToCourt
Context triple: [Tariefcommissie (Netherlands), referredToCourt, Court of Justice of the European Union]
  • A. introducedToCourt
    Indicates that an entity has been formally presented or brought before a court or judicial body for consideration or action.
  • B. broughtToCourtBy
    Indicates that a person or entity is taken to court or legally prosecuted by another party.
  • C. requestedFromCourt
    Indicates that a party has formally asked a court to take a specific action or provide a particular ruling or document.
  • D. affectedCourt
    Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
  • E. destinationCourt chosen
    Indicates the court or judicial body to which a case, appeal, or legal matter is directed or transferred.
  • 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_69f76df28d8c819089f2c5799fe7d079 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fe68a4b67881909ca1d9f276f922e0 completed May 8, 2026, 10:50 p.m.
PD Predicate disambiguation batch_69fe680234c88190b01f953987b74972 completed May 8, 2026, 10:47 p.m.
Created at: May 3, 2026, 4:03 p.m.