Triple

T14932521
Position Surface form Disambiguated ID Type / Status
Subject Litoměřice E372303 entity
Predicate locatedOnRiver P165 FINISHED
Object Ohře E91943 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: Ohře | Statement: [Litoměřice, locatedOnRiver, Ohře]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ohře
Context triple: [Litoměřice, locatedOnRiver, Ohře]
  • A. Ohře chosen
    The Ohře is a river in Central Europe that flows through Germany and the Czech Republic before joining the Elbe.
  • B. Podyjí
    Podyjí is a protected national park area in the Czech Republic known for its deep Dyje River valley, diverse ecosystems, and well-preserved natural landscapes.
  • C. Brod nad Tichou
    Brod nad Tichou is a small municipality and village in the Plzeň Region of the Czech Republic.
  • D. Oľka
    Oľka is a river in eastern Slovakia that serves as one of the tributaries feeding into the Ondava River.
  • E. Hromovka
    Hromovka is a ski area and slope complex that forms part of the mountain resort town of Špindlerův Mlýn in the Krkonoše (Giant) Mountains of the Czech Republic.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded646a0808190ba5c0c91bde011c5 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe72c86b5c81909e601a3fc78276bd completed May 8, 2026, 11:33 p.m.
Created at: April 10, 2026, 2:37 a.m.