Triple

T17080475
Position Surface form Disambiguated ID Type / Status
Subject Mykhailo Verbytsky E414455 entity
Predicate burialPlace P196 FINISHED
Object Mlyny E1249671 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: Mlyny | Statement: [Mykhailo Verbytsky, burialPlace, Mlyny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mlyny
Context triple: [Mykhailo Verbytsky, burialPlace, Mlyny]
  • A. Mlyny chosen
    Mlyny is a village in present-day Poland historically associated with Ukrainian cultural figures, including as the place where composer Mykhailo Verbytsky died.
  • B. Fiala
    Fiala is a Czech surname most prominently associated with Petr Fiala, the Czech politician and Prime Minister.
  • C. Mumlava
    Mumlava is a river in the Krkonoše (Giant) Mountains of the Czech Republic, known for its scenic waterfalls and gorges near the town of Harrachov.
  • D. Hlubočky
    Hlubočky is a municipality and village in the Olomouc Region of the Czech Republic, known historically for its industrial facilities and proximity to the city of Olomouc.
  • E. Mlava
    Mlava is a river in eastern Serbia that flows through the Braničevo region before joining the Danube.
  • 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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbe24a6481908b4596c95220df4a completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0139f7e6408190978c940c6e641d47 completed May 11, 2026, 2:07 a.m.
Created at: April 10, 2026, 5:34 a.m.