Triple

T31460982
Position Surface form Disambiguated ID Type / Status
Subject Ploshchad Vozrozhdeniya E802591 entity
Predicate hasNameInLanguage P15 FINISHED
Object Площадь Возрождения
Площадь Возрождения — это станция Петербургского метрополитена на Кировско-Выборгской линии, расположенная в Калининском районе Санкт-Петербурга.
E1963992 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: [Ploshchad Vozrozhdeniya, hasNameInLanguage, Площадь Возрождения]
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: [Ploshchad Vozrozhdeniya, hasNameInLanguage, Площадь Возрождения]
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_69f348c678ac81908a2e950867619061 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a14caa588190acf6de6d803b6bc7 completed May 3, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b078f131c8190b33bfda79ab04a04 completed June 11, 2026, 7:07 p.m.
NEDg Description generation batch_6a2b0bdd4ff881908a851a734b7a4271 completed June 11, 2026, 7:26 p.m.
NED2 Entity disambiguation (via description) batch_6a2b0dbea4948190947da4123f2600a9 completed June 11, 2026, 7:34 p.m.
Created at: April 30, 2026, 9:19 p.m.