Triple

T1493549
Position Surface form Disambiguated ID Type / Status
Subject UEFA Super Cup E29635 entity
Predicate venuePolicy P28629 FINISHED
Object single neutral venue selected by UEFA 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: single neutral venue selected by UEFA | Statement: [UEFA Super Cup, venuePolicy, single neutral venue selected by UEFA]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: venuePolicy
Context triple: [UEFA Super Cup, venuePolicy, single neutral venue selected by UEFA]
  • A. reservationPolicy
    Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
  • B. farePolicySupport
    Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
  • C. feePolicy
    Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
  • D. hasReservationPolicy
    Indicates that an entity specifies or is governed by a particular policy regarding how reservations are made, managed, or honored.
  • E. collectionPolicy
    Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
  • 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_69a498dba1d8819093b46a3a8d2485f1 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6c665488190ae665f7a1b0563f5 completed March 1, 2026, 11:07 p.m.
PD Predicate disambiguation batch_69a4c48902808190a8028d359bcf123e completed March 1, 2026, 10:58 p.m.
PDg Predicate description generation batch_69a4c52c703c8190a56389b09d97659f completed March 1, 2026, 11:01 p.m.
Created at: March 1, 2026, 8:12 p.m.