Triple

T34730942
Position Surface form Disambiguated ID Type / Status
Subject Dederkały Wielkie E1001208 entity
Predicate hasNameInLanguage P15 FINISHED
Object Великі Дедеркали (Ukrainian)
Великі Дедеркали — це село в Україні, відоме як адміністративний та історичний населений пункт у західній частині країни.
E2110483 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: [Dederkały Wielkie, hasNameInLanguage, Великі Дедеркали (Ukrainian)]
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: Великі Дедеркали (Ukrainian)
Triple: [Dederkały Wielkie, hasNameInLanguage, Великі Дедеркали (Ukrainian)]
Generated description
Великі Дедеркали — це село в Україні, відоме як адміністративний та історичний населений пункт у західній частині країни.

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_69f76daf739881909ed3554f98a2b433 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f779ad812881909c8e314409d4d2ca completed May 3, 2026, 4:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a375bedf74c8190aba79056e2d3f149 completed June 21, 2026, 3:35 a.m.
NEDg Description generation batch_6a375d09dfbc81909eddba9593dafbb2 completed June 21, 2026, 3:39 a.m.
NED2 Entity disambiguation (via description) batch_6a3760f4f2c88190998d890243e41710 completed June 21, 2026, 3:56 a.m.
Created at: May 3, 2026, 3:59 p.m.