Triple

T22478544
Position Surface form Disambiguated ID Type / Status
Subject Lillestrøm municipality E555698 entity
Predicate hasFootballStadium P5119 FINISHED
Object Åråsen Stadion 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: Åråsen Stadion | Statement: [Lillestrøm municipality, hasFootballStadium, Åråsen Stadion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Åråsen Stadion
Context triple: [Lillestrøm municipality, hasFootballStadium, Åråsen Stadion]
  • A. Åråsen Stadion chosen
    Å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.
  • B. Nadderud Stadion
    Nadderud Stadion is a football stadium in Bærum, Norway, best known as the long-time home ground of Norwegian club Stabæk Fotball.
  • C. Aspmyra Stadion
    Aspmyra Stadion is a football stadium in Bodø, Norway, best known as the home ground of FK Bodø/Glimt.
  • D. Vålerenga Stadion
    Vålerenga Stadion is a football stadium in Oslo, Norway, serving as the home ground of the Vålerenga Fotball club.
  • E. Fredrikstad Stadion
    Fredrikstad Stadion is a football stadium in Fredrikstad, Norway, primarily known as the modern home ground of the Norwegian club Fredrikstad FK.
  • 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_69e11e52c2048190952dc5df209b9bed completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15be653bc8190a2e5c47e38228bfe completed April 29, 2026, 1:16 a.m.
Created at: April 16, 2026, 8:49 p.m.