Triple

T20026423
Position Surface form Disambiguated ID Type / Status
Subject Bernolákovo E494993 entity
Predicate hasNameInSlovak P25642 FINISHED
Object Bernolákovo 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: Bernolákovo | Statement: [Bernolákovo, hasNameInSlovak, Bernolákovo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bernolákovo
Context triple: [Bernolákovo, hasNameInSlovak, Bernolákovo]
  • A. Bernolákovo chosen
    Bernolákovo is a village and municipality in western Slovakia, situated near Bratislava in the Bratislava Region.
  • B. Bavorovice
    Bavorovice is a small village in the South Bohemian Region of the Czech Republic, known for its traditional rural character and proximity to the town of Hluboká nad Vltavou.
  • C. Betlanovce
    Betlanovce is a village in eastern Slovakia historically linked to the influential noble Thurzó family.
  • D. Boskovice
    Boskovice is a historic town in the South Moravian Region of the Czech Republic, known for its preserved Jewish quarter, castle ruins, and cultural heritage.
  • E. Borohrádek
    Borohrádek is a small town in the Hradec Králové Region of the Czech Republic.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6628e1eec81908e4c9b2b0b68f0e4 completed April 20, 2026, 5:29 p.m.
Created at: April 11, 2026, 3:35 p.m.