Triple

T24251363
Position Surface form Disambiguated ID Type / Status
Subject Yelizovo E603533 entity
Predicate administrativeCenterOf P383 FINISHED
Object Yelizovsky District
Yelizovsky District is an administrative district in Kamchatka Krai, Russia, encompassing the area around the town of Yelizovo on the Kamchatka Peninsula.
E1957202 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: Yelizovsky District | Statement: [Yelizovo, administrativeCenterOf, Yelizovsky District]
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: Yelizovsky District
Triple: [Yelizovo, administrativeCenterOf, Yelizovsky District]
Generated description
Yelizovsky District is an administrative district in Kamchatka Krai, Russia, encompassing the area around the town of Yelizovo on the Kamchatka Peninsula.

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_69e29540da0481909a38bdae315b7a02 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28b89eb8081909ccf37081add5cee completed April 29, 2026, 10:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2a1e014f008190a6f84a9ddd32eca7 completed June 11, 2026, 2:31 a.m.
NEDg Description generation batch_6a2a2823d8408190b62a5e80e6878daf completed June 11, 2026, 3:14 a.m.
NED2 Entity disambiguation (via description) batch_6a2a288b41bc8190bfdc652f18191347 completed June 11, 2026, 3:16 a.m.
Created at: April 18, 2026, 12:05 a.m.