Triple

T10013263
Position Surface form Disambiguated ID Type / Status
Subject Nemyriv E199425 entity
Predicate locatedNear P294 FINISHED
Object city of Vinnytsia E213949 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: city of Vinnytsia | Statement: [Nemyriv, locatedNear, city of Vinnytsia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Vinnytsia
Context triple: [Nemyriv, locatedNear, city of Vinnytsia]
  • A. Vinnytsia chosen
    Vinnytsia is a major city in central Ukraine known as an important administrative, economic, and cultural center on the Southern Bug River.
  • B. Kropyvnytskyi
    Kropyvnytskyi is a regional city in central Ukraine known as an important administrative, cultural, and transportation center.
  • C. Myrhorod
    Myrhorod is a historic city in central Ukraine, known for its mineral springs and as the setting of several stories by writer Nikolai Gogol.
  • D. Nizhyn
    Nizhyn is a historic city in northern Ukraine known for its cultural heritage, educational institutions, and well-preserved architecture.
  • E. Kremenchuk
    Kremenchuk is an industrial city in central Ukraine on the Dnieper River, historically significant as a major transport and strategic hub.
  • 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_69ca8315a1a08190ab310f25620f362b completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd3e35508190920468be167cb708 completed April 2, 2026, 1:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69d26a858c848190887a035a9ac04c5e completed April 5, 2026, 1:58 p.m.
Created at: March 30, 2026, 8:52 p.m.