Triple

T20898660
Position Surface form Disambiguated ID Type / Status
Subject Emil Hácha E514609 entity
Predicate familyName P18 FINISHED
Object Hácha NE NERFINISHED

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: Hácha | Statement: [Emil Hácha, familyName, Hácha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hácha
Context triple: [Emil Hácha, familyName, Hácha]
  • A. Hácha chosen
    Hácha is a Czech surname most notably borne by Emil Hácha, the third President of Czechoslovakia who served during the early years of World War II.
  • B. Gabčík
    Gabčík is a Slovak surname most notably borne by Jozef Gabčík, a World War II resistance fighter involved in the assassination of Nazi official Reinhard Heydrich.
  • C. Havlick
    Havlick is a surname most notably associated with American film editor Gene Havlick, known for his work during Hollywood’s classic era.
  • D. Hájek
    Hájek is a Czech surname borne by numerous notable figures in fields such as politics, science, and the arts.
  • E. Krompachy
    Krompachy is a small industrial town in eastern Slovakia known historically for its ironworks and metalworking industry.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4f7ebe48190952a85547a0f31a1 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6e8f826788190b11008cc94b2a4e4 completed April 21, 2026, 3:03 a.m.
Created at: April 16, 2026, 12:47 p.m.