Triple

T12569799
Position Surface form Disambiguated ID Type / Status
Subject Domažlice District E295570 entity
Predicate hasMunicipality P847 FINISHED
Object Holýšov E304852 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: Holýšov | Statement: [Domažlice District, hasMunicipality, Holýšov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holýšov
Context triple: [Domažlice District, hasMunicipality, Holýšov]
  • A. Holýšov chosen
    Holýšov is a town in the Czech Republic known for its industrial history and location in the western Plzeň Region.
  • B. Hronov
    Hronov is a small town in the Hradec Králové Region of the Czech Republic, known as the birthplace of writer Alois Jirásek and for its traditional cultural events.
  • C. Lovosice
    Lovosice is a town in the Czech Republic, historically notable as the site of the 1756 Battle of Lobositz during the Seven Years' War.
  • D. Třemošná
    Třemošná is a small town in the western Czech Republic, located near the city of Plzeň in the Plzeň Region.
  • E. Pohořelice
    Pohořelice is a small town in the South Moravian Region of the Czech Republic, known for its agricultural surroundings and proximity to the city of Brno.
  • 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_69d6ad9cac2c81908e8a7bed82d1e21d completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d954a422c88190a22cc34d2eac00ce completed April 10, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65eb8ec888190b46a0b48840efd20 completed May 2, 2026, 8:29 p.m.
Created at: April 8, 2026, 11:50 p.m.