Triple

T16371559
Position Surface form Disambiguated ID Type / Status
Subject Ivan Hlinka E397575 entity
Predicate familyName P18 FINISHED
Object Hlinka E397575 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: Hlinka | Statement: [Ivan Hlinka, familyName, Hlinka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hlinka
Context triple: [Ivan Hlinka, familyName, Hlinka]
  • A. Hlinka chosen
    Hlinka is a Czech and Slovak surname most prominently associated with legendary Czech ice hockey player and coach Ivan Hlinka.
  • B. Hlinka Guard
    The Hlinka Guard was a fascist paramilitary organization in the Slovak State during World War II, known for its collaboration with Nazi Germany and participation in the persecution of Jews and political opponents.
  • C. Ruzinov
    Ružinov is a borough of Bratislava, Slovakia, known as a major residential and commercial district of the capital.
  • D. Děčínský Sněžník
    Děčínský Sněžník is a prominent table mountain in the Czech Republic known for its sandstone cliffs and panoramic views over the surrounding Elbe Sandstone landscape.
  • E. Baník
    Baník is a Czech football club from Ostrava known for its passionate fan base and rich history in the country’s top league.
  • 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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2ff420d04819096ff12e08edf2f8b completed April 18, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_6a002dc44c508190bf87b437d1447db6 completed May 10, 2026, 7:03 a.m.
Created at: April 10, 2026, 5:08 a.m.