Triple

T17327066
Position Surface form Disambiguated ID Type / Status
Subject HCKE E420712 entity
Predicate homeArena P373 FINISHED
Object Steel Aréna E420710 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: Steel Aréna | Statement: [HCKE, homeArena, Steel Aréna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Steel Aréna
Context triple: [HCKE, homeArena, Steel Aréna]
  • A. Steel Aréna chosen
    Steel Aréna is a modern multi-purpose indoor arena in Košice, Slovakia, best known as the home venue of the ice hockey club HC Košice and for hosting major sporting and cultural events.
  • B. MOL Aréna
    MOL Aréna is a football stadium in Dunajská Streda, Slovakia, primarily serving as the home ground of the local club FC DAC 1904.
  • C. Královka Arena
    Královka Arena is a multi-purpose indoor sports hall in Prague, Czech Republic, primarily used for basketball and other indoor events.
  • D. VEB Arena
    VEB Arena is a modern football stadium in Moscow, Russia, best known as the home ground of CSKA Moscow and a key venue for major city derbies.
  • E. Voith-Arena
    Voith-Arena is a football stadium in Heidenheim, Germany, primarily known as the venue for 1. FC Heidenheim’s home matches.
  • 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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e439d321c881909e63a6870b152c8c completed April 19, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01954ecadc8190a6484ff0a207fe9b completed May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:43 a.m.