Triple

T10088416
Position Surface form Disambiguated ID Type / Status
Subject Třešť E215279 entity
Predicate hasRailwayConnectionTo P3791 FINISHED
Object Telč E695949 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: Telč | Statement: [Třešť, hasRailwayConnectionTo, Telč]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Telč
Context triple: [Třešť, hasRailwayConnectionTo, Telč]
  • A. Telč chosen
    Telč is a historic Czech town renowned for its well-preserved Renaissance and Baroque square, which is listed as a UNESCO World Heritage Site.
  • B. Ptuj
    Ptuj is one of Slovenia’s oldest towns, renowned for its well-preserved medieval architecture and rich cultural heritage along the Drava River.
  • C. Lučenec
    Lučenec is a town in southern Slovakia known as a regional center of trade, transport, and culture in the Novohrad area.
  • D. Tatura
    Tatura is a rural town in northern Victoria, Australia, known for its agricultural industries and historical World War II internment camps.
  • E. Lovech
    Lovech is a historic city in north-central Bulgaria, known for its medieval fortress, picturesque old town, and important role during the Second Bulgarian Empire.
  • 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_69ca83a1eed081908b2e9580f2ebeea7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd04875748190a81d1e9ad68dda96 completed April 2, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b693afac819090635d2eb147bdcb completed April 5, 2026, 7:22 p.m.
Created at: March 30, 2026, 9:01 p.m.