Triple

T16709596
Position Surface form Disambiguated ID Type / Status
Subject HC Karlovy Vary E406067 entity
Predicate hasRival P1375 FINISHED
Object HC Plzeň E107836 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: HC Plzeň | Statement: [HC Karlovy Vary, hasRival, HC Plzeň]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HC Plzeň
Context triple: [HC Karlovy Vary, hasRival, HC Plzeň]
  • A. HC Škoda Plzeň chosen
    HC Škoda Plzeň is a professional Czech ice hockey club based in Plzeň that competes in the country’s top-tier league.
  • B. HC Pardubice
    HC Pardubice is a prominent Czech professional ice hockey club based in Pardubice, known for its rich history in the Czech Extraliga and development of elite players.
  • C. HC Lev Praha
    HC Lev Praha was a professional ice hockey club based in Prague, Czech Republic, that competed in the Kontinental Hockey League (KHL).
  • D. HC České Budějovice
    HC České Budějovice is a professional ice hockey club from České Budějovice, Czech Republic, known for its long-standing presence in the country’s top-tier competitions.
  • E. HC Zlín
    HC Zlín is a professional ice hockey club from Zlín, Czech Republic, known for competing in the country’s top leagues and developing notable Czech players.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3865186b48190bb45a761f5cf1a83 completed April 18, 2026, 1:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0091a739308190b4d645e096d1710b completed May 10, 2026, 2:09 p.m.
Created at: April 10, 2026, 5:20 a.m.