Triple

T8978580
Position Surface form Disambiguated ID Type / Status
Subject Ostravice E214462 entity
Predicate givesNameTo P63 FINISHED
Object Ostravice (town) 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 (town) | Statement: [Ostravice, givesNameTo, Ostravice (town)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostravice (town)
Context triple: [Ostravice, givesNameTo, Ostravice (town)]
  • 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. Ostrava-Kunčičky
    Ostrava-Kunčičky is a district of the city of Ostrava in the Czech Republic, known as the area where the Ostrava Zoo is situated.
  • C. Hořovice
    Hořovice is a small Czech town known for its historic chateau and location in the western part of the Central Bohemian Region.
  • D. Tasovice
    Tasovice is a village in the Czech Republic known as the birthplace of the Redemptorist priest and saint Clement Mary Hofbauer.
  • E. Blovice
    Blovice is a small town in the Czech Republic that serves as a local administrative and service center in the Plzeň 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67a4b3e88190b778a9b5589cab6d completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfd0afe9688190bdd66198ab31c2c7 completed April 3, 2026, 2:37 p.m.
Created at: March 30, 2026, 7:03 p.m.