Triple

T11640137
Position Surface form Disambiguated ID Type / Status
Subject Tromsø IL E276636 entity
Predicate hasRival P1375 FINISHED
Object Bodø/Glimt E378092 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: Bodø/Glimt | Statement: [Tromsø IL, hasRival, Bodø/Glimt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bodø/Glimt
Context triple: [Tromsø IL, hasRival, Bodø/Glimt]
  • A. FK Bodø/Glimt chosen
    FK Bodø/Glimt is a Norwegian professional football club known for its attacking style of play and recent domestic success, including historic league titles.
  • B. Bryne FK
    Bryne FK is a Norwegian football club known for developing striker Erling Haaland in its youth system.
  • C. Sarpsborg 08 FF
    Sarpsborg 08 FF is a Norwegian professional football club based in Sarpsborg that competes in the country’s top division, the Eliteserien.
  • D. Lillestrøm SK
    Lillestrøm SK is a Norwegian professional football club known for its passionate fan base, historic success in domestic competitions, and intense rivalry with other Oslo-area teams.
  • E. Vålerenga
    Vålerenga is a neighborhood in Oslo, Norway, known for its working-class roots and strong association with the local football club Vålerenga Fotball.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a25e90c08190b7fb73939a2be3d7 completed April 10, 2026, 7:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ee87deb3888190842bd61efd7b3989 completed April 26, 2026, 9:47 p.m.
Created at: April 8, 2026, 9:39 p.m.