Triple

T34000085
Position Surface form Disambiguated ID Type / Status
Subject Chemerivtsi E871790 entity
Predicate formerAdministrativeCenterOf P23608 FINISHED
Object Chemerivtsi Raion
Chemerivtsi Raion was a former administrative district in Khmelnytskyi Oblast, western Ukraine, that existed until Ukraine’s 2020 administrative reform.
E2156288 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: Chemerivtsi Raion | Statement: [Chemerivtsi, formerAdministrativeCenterOf, Chemerivtsi Raion]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Chemerivtsi Raion
Triple: [Chemerivtsi, formerAdministrativeCenterOf, Chemerivtsi Raion]
Generated description
Chemerivtsi Raion was a former administrative district in Khmelnytskyi Oblast, western Ukraine, that existed until Ukraine’s 2020 administrative reform.

Provenance (5 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_69f3499f8cbc81908de6ec89fa91ea8f completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f70ac23f94819080fac25660f9e75d completed May 3, 2026, 8:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a389144051c8190bbbcb40b78ffd733 completed June 22, 2026, 1:35 a.m.
NEDg Description generation batch_6a389253d4f881909a40e2c14b4a6d4e completed June 22, 2026, 1:39 a.m.
NED2 Entity disambiguation (via description) batch_6a38930372408190a387347aba837518 completed June 22, 2026, 1:42 a.m.
Created at: May 1, 2026, 1:50 a.m.