Triple

T23072628
Position Surface form Disambiguated ID Type / Status
Subject Hrádeček E575236 entity
Predicate locatedNear P294 FINISHED
Object Trutnov 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: Trutnov | Statement: [Hrádeček, locatedNear, Trutnov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trutnov
Context triple: [Hrádeček, locatedNear, Trutnov]
  • A. Trutnov chosen
    Trutnov is a town in the Czech Republic known as a gateway to the eastern Krkonoše (Giant Mountains) region and for its historical center and industrial heritage.
  • B. Hroznětín
    Hroznětín is a small historic town in the Karlovy Vary Region of the Czech Republic, known for its location near the Ore Mountains.
  • C. Třebovka
    Třebovka is a river in the Czech Republic that flows through the Pardubice Region before joining the Tichá Orlice.
  • D. Chrudim
    Chrudim is a historic town in the Pardubice Region of the Czech Republic, known for its well-preserved medieval center and cultural heritage.
  • E. Tišnov
    Tišnov is a small historic town in the South Moravian Region of the Czech Republic, located northwest of Brno.
  • 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_69e245be28d48190ad1348d5a73db37d completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18c60fa6c81908496f181c7d62033 completed April 29, 2026, 4:43 a.m.
Created at: April 17, 2026, 3:56 p.m.