Triple

T15183779
Position Surface form Disambiguated ID Type / Status
Subject Volkswagen Arena E362813 entity
Predicate hasUEFARating P6315 FINISHED
Object UEFA Category 4 stadium 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: UEFA Category 4 stadium | Statement: [Volkswagen Arena, hasUEFARating, UEFA Category 4 stadium]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUEFARating
Context triple: [Volkswagen Arena, hasUEFARating, UEFA Category 4 stadium]
  • A. hasUEFACoefficientRanking
    Indicates that an entity is associated with a specific position or value in UEFA’s official coefficient ranking system.
  • B. hasUEFACategory chosen
    Indicates that an entity is classified under a specific UEFA-defined category or tier.
  • C. fifaEligibilityRule
    Indicates that a person meets the official criteria set by FIFA to represent a particular national team in international football competitions.
  • D. fifaRecognized
    Indicates that an organization, competition, or entity is officially recognized or sanctioned by FIFA as meeting its standards or falling under its authority.
  • E. levelInUEFASystem
    Indicates the specific tier or division an entity occupies within the hierarchical structure of the UEFA football league system.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e006674c088190ba635a78c30f5637 completed April 15, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69deb97bd8bc8190b2ad4888f97cf963 completed April 14, 2026, 10:02 p.m.
Created at: April 10, 2026, 3:09 a.m.