Triple

T9207133
Position Surface form Disambiguated ID Type / Status
Subject Moravian-Silesian Region E221010 entity
Predicate hasRiver P165 FINISHED
Object Ostravice E214462 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: Ostravice | Statement: [Moravian-Silesian Region, hasRiver, Ostravice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostravice
Context triple: [Moravian-Silesian Region, hasRiver, Ostravice]
  • A. Ostravice chosen
    Ostravice is a river in the Czech Republic that flows through the Moravian-Silesian region and gives its name to the town of Ostravice and partly to the city of Ostrava.
  • B. Lovosice
    Lovosice is a town in the Czech Republic, historically notable as the site of the 1756 Battle of Lobositz during the Seven Years' War.
  • C. Blovice
    Blovice is a small town in the Czech Republic that serves as a local administrative and service center in the Plzeň Region.
  • D. Mikulov
    Mikulov is a historic wine-producing town in the South Moravian region of the Czech Republic, known for its chateau, picturesque old town, and proximity to the Pálava Hills.
  • E. Říčany
    Říčany is a town in the Czech Republic, located just southeast of Prague and known as a popular residential and commuter suburb with historical roots.
  • 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_69ca83e9d0e081908bdb71097201a06c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd9b0b6788190908bee67a0c5d48f completed April 1, 2026, 8:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23c8f14b081909df4eae9b2d16860 completed April 5, 2026, 10:42 a.m.
Created at: March 30, 2026, 7:26 p.m.