Triple

T3145632
Position Surface form Disambiguated ID Type / Status
Subject Frölunda HC E65756 entity
Predicate playsHomeGamesAt P890 FINISHED
Object Frölundaborg E331599 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: Frölundaborg | Statement: [Frölunda HC, playsHomeGamesAt, Frölundaborg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frölundaborg
Context triple: [Frölunda HC, playsHomeGamesAt, Frölundaborg]
  • A. Frölundaborg chosen
    Frölundaborg is an indoor ice hockey arena in Gothenburg, Sweden, best known as one of the primary venues for the professional club Frölunda HC.
  • B. Alfheim Stadion
    Alfheim Stadion is a football stadium in Tromsø, Norway, best known as the home ground of the Norwegian club Tromsø IL.
  • C. Råsunda
    Råsunda is a district in Solna, Sweden, historically known for hosting the former Råsunda Stadium, once the national football arena.
  • D. Åråsen Stadion
    Åråsen Stadion is a football stadium in Lillestrøm, Norway, best known as the main home ground of Lillestrøm SK and a prominent venue in Norwegian football.
  • E. Briskeby Arena
    Briskeby Arena is a football stadium in Hamar, Norway, primarily used as the home ground of the club HamKam.
  • 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_69ad8582f564819088c27e1f96153938 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada59797788190a8d71262888c5df0 completed March 8, 2026, 4:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69b235bad36c8190ab93312950380d36 completed March 12, 2026, 3:40 a.m.
Created at: March 8, 2026, 3:05 p.m.