Triple

T33032784
Position Surface form Disambiguated ID Type / Status
Subject Sievierodonetsk E845212 entity
Predicate hasNameInUkrainian P1435 FINISHED
Object Сєвєродонецьк
Сєвєродонецьк is an industrial city in eastern Ukraine’s Luhansk Oblast, known for its chemical industry and as a focal point of military conflict in the Donbas region.
E2034004 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: Сєвєродонецьк | Statement: [Sievierodonetsk, hasNameInUkrainian, Сєвєродонецьк]
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: Сєвєродонецьк
Triple: [Sievierodonetsk, hasNameInUkrainian, Сєвєродонецьк]
Generated description
Сєвєродонецьк is an industrial city in eastern Ukraine’s Luhansk Oblast, known for its chemical industry and as a focal point of military conflict in the Donbas region.

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_69f34951348c8190b56746b0a7018182 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d2e6139881909a3cb8b4a78fa67c completed May 3, 2026, 4:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34e50e5fb4819091f497eddf4a3244 completed June 19, 2026, 6:43 a.m.
NEDg Description generation batch_6a34e5e7ca0c8190b09741dfb9c7bdb0 completed June 19, 2026, 6:47 a.m.
NED2 Entity disambiguation (via description) batch_6a34e70605548190895680498d4f6066 completed June 19, 2026, 6:51 a.m.
Created at: May 1, 2026, 1:24 a.m.