Triple

T36561637
Position Surface form Disambiguated ID Type / Status
Subject Heineken Cup E901852 entity
Predicate secondaryCompetitionRelated P65871 FINISHED
Object European Challenge Cup 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: European Challenge Cup | Statement: [Heineken Cup, secondaryCompetitionRelated, European Challenge Cup]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryCompetitionRelated
Context triple: [Heineken Cup, secondaryCompetitionRelated, European Challenge Cup]
  • A. secondaryCompetition chosen
    Indicates that one entity participates in or is involved with a secondary or subordinate competition relative to a primary one.
  • B. centralCompetition
    Indicates a primary or core competitive relationship or contest that is central to the interaction between the entities.
  • C. primaryCompetition
    Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
  • D. secondaryOpponent
    Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
  • E. tertiaryCompetition
    Indicates a competitive relationship that occurs at a third or lower-priority level, typically after primary and secondary competitions have been considered.
  • 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_69f76e634e9481908c9ba1b87ab87c26 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ff6fba1a5c8190a660279a6271d785 completed May 9, 2026, 5:32 p.m.
PD Predicate disambiguation batch_69ff6f59388c8190a7d6ab7bc7705bc0 completed May 9, 2026, 5:31 p.m.
Created at: May 3, 2026, 4:11 p.m.