Triple

T20850242
Position Surface form Disambiguated ID Type / Status
Subject Gamla Ullevi E513337 entity
Predicate replaced P101 FINISHED
Object Old Gamla Ullevi stadium 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: Old Gamla Ullevi stadium | Statement: [Gamla Ullevi, replaced, Old Gamla Ullevi stadium]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Gamla Ullevi stadium
Context triple: [Gamla Ullevi, replaced, Old Gamla Ullevi stadium]
  • A. Gamla Ullevi chosen
    Gamla Ullevi is a football stadium in Gothenburg, Sweden, primarily used for professional club matches and major football events.
  • B. Viking Stadion
    Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
  • C. Ullevi Stadium
    Ullevi Stadium is a major multi-purpose arena in Gothenburg, Sweden, known for hosting large football matches, athletics events, and concerts.
  • D. Daknamstadion
    Daknamstadion is a football stadium in Lokeren, Belgium, best known as the long-time home ground of K.S.C. Lokeren Oost-Vlaanderen.
  • E. Alfheim Stadion
    Alfheim Stadion is a football stadium in Tromsø, Norway, best known as the home ground of the Norwegian club Tromsø IL.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4f4898081908209e58edb8f9c45 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c352ca8c819094545dbe67bfe3dc completed April 21, 2026, 12:22 a.m.
Created at: April 16, 2026, 12:43 p.m.