Triple

T3869302
Position Surface form Disambiguated ID Type / Status
Subject Ohře E91943 entity
Predicate flowsThrough P225 FINISHED
Object Litoměřice E372303 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: Litoměřice | Statement: [Ohře, flowsThrough, Litoměřice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Litoměřice
Context triple: [Ohře, flowsThrough, Litoměřice]
  • A. Litoměřice chosen
    Litoměřice is a historic town in the Ústí nad Labem Region of the Czech Republic, known for its well-preserved architecture and location at the confluence of the Elbe and Ohře rivers.
  • B. Jihlava
    Jihlava is a historic city in the Czech Republic, known as one of the country’s oldest mining towns and a regional cultural and administrative center.
  • C. Plzeň
    Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
  • D. České Budějovice
    České Budějovice is a historic city in the Czech Republic known for its medieval architecture and as the original home of Budweiser Budvar beer.
  • E. Olomouc
    Olomouc is a historic city in the eastern Czech Republic known for its well-preserved old town, Baroque architecture, and UNESCO-listed Holy Trinity Column.
  • 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_69aed9645f348190a9868e7cef56ab7e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec533828819080f52dae15fdbecd completed March 9, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f0ebb588190bb7a935e066f9e4b completed March 14, 2026, 3:30 p.m.
Created at: March 9, 2026, 3:20 p.m.