Triple

T15021463
Position Surface form Disambiguated ID Type / Status
Subject FK Bodø/Glimt E378092 entity
Predicate hasRivalryWith P893 FINISHED
Object Tromsø IL E276636 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: Tromsø IL | Statement: [FK Bodø/Glimt, hasRivalryWith, Tromsø IL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tromsø IL
Context triple: [FK Bodø/Glimt, hasRivalryWith, Tromsø IL]
  • A. Tromsø IL chosen
    Tromsø IL is a Norwegian professional football club based in the city of Tromsø, known for competing in the country’s top divisions and for being one of the world’s northernmost elite clubs.
  • B. 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.
  • C. 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.
  • D. Mjøndalen
    Mjøndalen is a town in Viken county, Norway, known historically for its industry and for its football club Mjøndalen IF.
  • E. Bryne FK
    Bryne FK is a Norwegian football club known for developing striker Erling Haaland in its youth system.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded765462c819097f331c9b39c80e3 completed April 15, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69feb7d956808190a3f17ef14c21d3af completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 2:56 a.m.