Triple

T13401906
Position Surface form Disambiguated ID Type / Status
Subject Arena Riga E319849 entity
Predicate alternativeName P39 FINISHED
Object Arēna Rīga E319849 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: Arēna Rīga | Statement: [Arena Riga, alternativeName, Arēna Rīga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arēna Rīga
Context triple: [Arena Riga, alternativeName, Arēna Rīga]
  • A. Arena Riga chosen
    Arena Riga is a major indoor sports and entertainment venue in Riga, Latvia, best known for hosting top-level ice hockey games and large-scale concerts and events.
  • B. Žalgiris Arena
    Žalgiris Arena is a modern multi-purpose indoor arena in Kaunas, Lithuania, best known as the home venue of the basketball club Žalgiris Kaunas and for hosting major sports and entertainment events.
  • C. Alytus Arena
    Alytus Arena is a multi-purpose indoor sports and events venue located in the city of Alytus, Lithuania.
  • D. Sazka Arena
    Sazka Arena is a major indoor ice hockey and multi-purpose arena in Prague, Czech Republic, known for hosting international sporting events and concerts.
  • E. 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.
  • 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_69d806b943cc8190b6af624d385d7e12 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbae4982e0819087a9fcb2fa88541f completed April 12, 2026, 2:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69f73983b8f08190bf4d1a64c0beab97 completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:34 p.m.