Triple

T36561638
Position Surface form Disambiguated ID Type / Status
Subject Heineken Cup E901852 entity
Predicate finalVenueVariedBySeason P198302 FINISHED
Object true 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: true | Statement: [Heineken Cup, finalVenueVariedBySeason, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: finalVenueVariedBySeason
Context triple: [Heineken Cup, finalVenueVariedBySeason, true]
  • A. hasSummerVenue
    Indicates that an entity uses or is associated with a particular venue specifically for summer activities or during the summer season.
  • B. hasSeasonalEvents
    Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
  • C. isTemporaryVenueFor
    Indicates that one place serves as a non-permanent or short-term location for hosting an event, activity, or organization.
  • D. returnedAsSeasonalAttraction
    Indicates that an entity that was previously unavailable has come back into use or display specifically as a limited-time or seasonal attraction.
  • E. internationalVenueFor
    Indicates that a location serves as a host or site for events, activities, or functions involving participants or audiences from multiple countries.
  • 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_69f76e634e9481908c9ba1b87ab87c26 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fed83b1d188190a318b0ad3003200a completed May 9, 2026, 6:46 a.m.
PD Predicate disambiguation batch_69fed78e03548190b6e6ad93ae8d131d completed May 9, 2026, 6:43 a.m.
PDg Predicate description generation batch_69fed83a3b8c819092a3bd1ca9d9b38b completed May 9, 2026, 6:46 a.m.
Created at: May 3, 2026, 4:11 p.m.