Triple

T13859384
Position Surface form Disambiguated ID Type / Status
Subject Narripaidat E333147 entity
Predicate refersTo P37 FINISHED
Object Jokerit E66429 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: Jokerit | Statement: [Narripaidat, refersTo, Jokerit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jokerit
Context triple: [Narripaidat, refersTo, Jokerit]
  • A. Jokerit chosen
    Jokerit is a professional ice hockey club from Helsinki, Finland, known as one of the country’s most successful and popular teams.
  • B. HIFK Helsinki
    HIFK Helsinki is a prominent professional ice hockey club from Helsinki, Finland, known as one of the country’s most successful and traditional teams in the Liiga.
  • C. Ilves
    Ilves is a prominent Finnish sports club from Tampere best known for its ice hockey team competing in the country’s top professional league.
  • D. Joensuu Wolves
    Joensuu Wolves is a sports club based in Joensuu, Finland, best known for representing the city in competitive team sports.
  • E. Porin Ässät
    Porin Ässät is a Finnish professional ice hockey club based in the city of Pori, competing in the country’s top-tier Liiga.
  • 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_69d81c5ba13c8190839315f54768acfd completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02de38e48190b6ead95561031c32 completed April 14, 2026, 9:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69fcdeefd61c81908d189237af45467a completed May 7, 2026, 6:50 p.m.
Created at: April 9, 2026, 10:14 p.m.