Triple

T16684137
Position Surface form Disambiguated ID Type / Status
Subject Ohře Valley E405414 entity
Predicate contains P35 FINISHED
Object Louny E416018 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: Louny | Statement: [Ohře Valley, contains, Louny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Louny
Context triple: [Ohře Valley, contains, Louny]
  • A. Louny chosen
    Louny is a historic town in the Ústí nad Labem Region of the Czech Republic known for its medieval architecture and location in the fertile Ohře River valley.
  • B. Chrudim
    Chrudim is a historic town in the Pardubice Region of the Czech Republic, known for its well-preserved medieval center and cultural heritage.
  • C. Rumburk
    Rumburk is a small historic town in the northern Czech Republic, near the German border, known for its Baroque architecture and location in the Šluknov Hook region.
  • D. Chýnov
    Chýnov is a small historic town in the South Bohemian Region of the Czech Republic, known for the nearby Chýnov Cave and its traditional architecture.
  • E. Harrachov
    Harrachov is a Czech mountain town in the Krkonoše range known as a major ski and winter sports resort near the Polish border.
  • 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_69d8838c28748190b3f5967c743940ab completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37d71a66881908c8d06cc074fdf29 completed April 18, 2026, 12:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0139e5f5988190a87b62d32bfb32fa completed May 11, 2026, 2:07 a.m.
Created at: April 10, 2026, 5:19 a.m.