Triple

T27466105
Position Surface form Disambiguated ID Type / Status
Subject EU adequacy decisions E693180 entity
Predicate subjectToChallengeBy P15175 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: [EU adequacy decisions, subjectToChallengeBy, Court of Justice of the European Union]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subjectToChallengeBy
Context triple: [EU adequacy decisions, subjectToChallengeBy, Court of Justice of the European Union]
  • A. mayBeChallengedBy chosen
    Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
  • B. canBeChallengedOn
    Indicates that one entity’s claim, decision, or status is open to being questioned, disputed, or formally contested by another entity.
  • C. challengeTo
    Indicates that one entity issues a challenge or dare for another entity to face or respond to.
  • D. hasBeenChallengedFor
    Indicates that an entity has been formally questioned, disputed, or contested specifically in relation to another entity or issue.
  • E. issuedChallengeFor
    Indicates that one entity has formally presented or posed a challenge for another entity to undertake or respond to.
  • 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_69ef538105548190a771cc5a0cf8c211 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f6a28c7c148190bfc980aad9f678ca completed May 3, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69f69fe1e3c88190830bb2e9f407357e completed May 3, 2026, 1:07 a.m.
Created at: April 27, 2026, 12:52 p.m.