Triple

T3010280
Position Surface form Disambiguated ID Type / Status
Subject German-Czech border E82198 entity
Predicate hasMajorBorderRiver 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: [German-Czech border, hasMajorBorderRiver, Ohře]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ohře
Context triple: [German-Czech border, hasMajorBorderRiver, 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. Topľa
    Topľa is a river in eastern Slovakia that flows through the Prešov Region before joining the Ondava River.
  • C. Hořice
    Hořice is a small Czech town known for its sandstone sculptures and traditional Hořice rolled wafers, located in the Hradec Králové Region.
  • D. Orzola
    Orzola is a small fishing village and port at the northern tip of Lanzarote in the Canary Islands, known as the main departure point for ferries to the nearby island of La Graciosa.
  • E. Šurany
    Šurany is a small town in southwestern Slovakia known for its agricultural surroundings and historical roots in the Nitra region.
  • 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_69ad8b1eb53481908c39bbcd1ec104b2 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9e11c4188190a3ae8fd0cbd8c2c0 completed March 8, 2026, 4:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e6410e481909753bef34e053363 completed March 11, 2026, 8:57 a.m.
Created at: March 8, 2026, 3 p.m.