Triple

T6246148
Position Surface form Disambiguated ID Type / Status
Subject Maramureș region E139724 entity
Predicate language P15 FINISHED
Object Ukrainian E73023 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: Ukrainian | Statement: [Maramureș region, language, Ukrainian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ukrainian
Context triple: [Maramureș region, language, Ukrainian]
  • A. Ukrainian language chosen
    Ukrainian language is an East Slavic language spoken primarily in Ukraine and written in a variant of the Cyrillic script.
  • B. Surzhyk
    Surzhyk is a mixed sociolect that blends elements of Ukrainian and Russian, commonly spoken in various regions of Ukraine.
  • C. Ukrainians
    Ukrainians are an East Slavic ethnic group native to Ukraine, characterized by their own language, culture, and national identity.
  • D. Ukrainka
    Ukrainka is a small city in northern Ukraine situated along the Dnipro River within the Kyiv metropolitan area.
  • E. Rusyn language
    The Rusyn language is an East Slavic minority language spoken by Rusyn communities in Central and Eastern Europe, particularly in parts of Ukraine, Slovakia, Poland, and Serbia.
  • 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_69c008b1c5088190ae6de2555fc05ad8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0631d9e648190a59ab4001f506424 completed March 22, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69c2440e47108190b07fa65db104e773 completed March 24, 2026, 7:58 a.m.
Created at: March 22, 2026, 4:23 p.m.