Triple

T13155644
Position Surface form Disambiguated ID Type / Status
Subject Orlice River E312579 entity
Predicate hasNameInLanguage P15 FINISHED
Object Orlice E312579 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: Orlice | Statement: [Orlice River, hasNameInLanguage, Orlice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orlice
Context triple: [Orlice River, hasNameInLanguage, Orlice]
  • A. Orlice
    Orlice is a river in the Czech Republic that flows through the city of Hradec Králové and is a tributary of the Labe (Elbe) River.
  • B. Orlice River chosen
    The Orlice River is a significant river in the Czech Republic that flows through eastern Bohemia and joins the Elbe near the city of Hradec Králové.
  • C. Pirna
    Pirna is a historic town in eastern Germany situated on the River Elbe, known as a gateway to the Saxon Switzerland National Park.
  • D. Velké Poříčí
    Velké Poříčí is a municipality and village in the Hradec Králové Region of the Czech Republic, situated near the town of Náchod close to the Polish border.
  • E. Weschnitz
    Weschnitz is a river in southwestern Germany that flows from the Odenwald hills through Hesse and Baden-Württemberg before joining the Rhine.
  • 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_69d806aabde48190899e13e41659cae5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c06ccb881909390df18e1a6f7ed completed April 10, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f71f1191e48190a504299a1f9afb2c completed May 3, 2026, 10:10 a.m.
Created at: April 9, 2026, 9:12 p.m.