Triple

T17273856
Position Surface form Disambiguated ID Type / Status
Subject Hodonín E419333 entity
Predicate hasTwinTown P919 FINISHED
Object Dubnica nad Váhom 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: Dubnica nad Váhom | Statement: [Hodonín, hasTwinTown, Dubnica nad Váhom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dubnica nad Váhom
Context triple: [Hodonín, hasTwinTown, Dubnica nad Váhom]
  • A. Dubnica nad Váhom chosen
    Dubnica nad Váhom is a town in western Slovakia known as an industrial center and the hometown of several notable Slovak athletes.
  • B. Vranov nad Topľou
    Vranov nad Topľou is a town in eastern Slovakia known as a local administrative and cultural center in the Prešov Region.
  • C. Nové Mesto nad Váhom
    Nové Mesto nad Váhom is a town in western Slovakia known for its location in the Váh River valley and its regional administrative and economic role.
  • D. Hlohovec
    Hlohovec is a town in western Slovakia known for its historic castle, vineyards, and location on the Váh River.
  • E. Žarnovica
    Žarnovica is a small town in central Slovakia known for its location in the Hron River valley and its traditional industrial and mining background.
  • 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_69d886da626481908a14ce7830329a35 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42f4c209c81909c713ed78f2cb19a completed April 19, 2026, 1:26 a.m.
Created at: April 10, 2026, 5:40 a.m.