Triple

T22226525
Position Surface form Disambiguated ID Type / Status
Subject Rosenborg Ballklub E549351 entity
Predicate homeStadium P890 FINISHED
Object Lerkendal 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: Lerkendal Stadion | Statement: [Rosenborg Ballklub, homeStadium, Lerkendal Stadion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lerkendal Stadion
Context triple: [Rosenborg Ballklub, homeStadium, Lerkendal Stadion]
  • A. Lerkendal Stadion chosen
    Lerkendal Stadion is a major football stadium in Trondheim, Norway, best known as the home ground of top Norwegian club Rosenborg BK.
  • B. Vålerenga Stadion
    Vålerenga Stadion is a football stadium in Oslo, Norway, serving as the home ground of the Vålerenga Fotball club.
  • C. 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.
  • 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. Å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.
  • 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_69e11e403d6481909a94d0aaf157f6ef completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12bee8de8819091ec5d14ea057f9e completed April 28, 2026, 9:51 p.m.
Created at: April 16, 2026, 8:37 p.m.