Triple

T13799726
Position Surface form Disambiguated ID Type / Status
Subject Gothia Towers E331606 entity
Predicate near P350 FINISHED
Object Scandinavium arena E333335 NE 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: Scandinavium arena | Statement: [Gothia Towers, near, Scandinavium arena]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scandinavium arena
Context triple: [Gothia Towers, near, Scandinavium arena]
  • A. Scandinavium arena chosen
    Scandinavium arena is a major indoor sports and entertainment venue in Gothenburg, Sweden, known for hosting ice hockey, concerts, and international events.
  • B. Skagerak Arena
    Skagerak Arena is a football stadium in Skien, Norway, best known as the home ground of the club Odds BK.
  • C. Briskeby Arena
    Briskeby Arena is a football stadium in Hamar, Norway, primarily used as the home ground of the club HamKam.
  • D. Visma Arena
    Visma Arena is a multi-purpose sports stadium in Växjö, Sweden, primarily used for football matches and home to local professional teams.
  • E. Läkerol Arena
    Läkerol Arena is the former name of a multi-purpose indoor ice hockey arena in Gävle, Sweden, that has hosted home games for the Brynäs IF hockey team.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d81c58feb08190a77bca8bf7d6d20f completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de025ce9148190b23370f6a522ff7a completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c70261c8819099408952f137456d completed May 3, 2026, 10:06 p.m.
Created at: April 9, 2026, 10:11 p.m.