Triple

T28080113
Position Surface form Disambiguated ID Type / Status
Subject Baikove Cemetery E709651 entity
Predicate operator P179 FINISHED
Object Kyiv municipal cemetery services
Kyiv municipal cemetery services is the city-run authority in Kyiv responsible for managing and maintaining public cemeteries and burial grounds.
E1802601 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: Kyiv municipal cemetery services | Statement: [Baikove Cemetery, operator, Kyiv municipal cemetery services]
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: Kyiv municipal cemetery services
Triple: [Baikove Cemetery, operator, Kyiv municipal cemetery services]
Generated description
Kyiv municipal cemetery services is the city-run authority in Kyiv responsible for managing and maintaining public cemeteries and burial grounds.

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_69ef9b7037f0819095bb90eaccbcaf32 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f640439f5c81909a39ab34ec1f0827 completed May 2, 2026, 6:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15c9166b2481909791a9198eb90178 completed May 26, 2026, 4:23 p.m.
NEDg Description generation batch_6a15caed4b148190b42af70ea0f6d872 completed May 26, 2026, 4:31 p.m.
NED2 Entity disambiguation (via description) batch_6a15cbdf46208190916381816f411f87 completed May 26, 2026, 4:35 p.m.
Created at: April 27, 2026, 8:51 p.m.