Triple

T30773746
Position Surface form Disambiguated ID Type / Status
Subject Prospekt Lenina E783601 entity
Predicate hasNameInRussian P20560 FINISHED
Object Проспект Ленина
Проспект Ленина — это одна из центральных магистралей, названных в честь Владимира Ленина и встречающихся во многих городах России и других стран бывшего СССР.
E2059075 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: [Prospekt Lenina, hasNameInRussian, Проспект Ленина]
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: [Prospekt Lenina, hasNameInRussian, Проспект Ленина]
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_69f224b1519081908b9db003fd2073e0 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68fc421dc8190862169489455a035 completed May 2, 2026, 11:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3611732d4881909af30651efed147c completed June 20, 2026, 4:05 a.m.
NEDg Description generation batch_6a361378069081909386b40cc20daffd completed June 20, 2026, 4:13 a.m.
NED2 Entity disambiguation (via description) batch_6a3613ef98f88190af545fbc5dd7ec59 completed June 20, 2026, 4:15 a.m.
Created at: April 29, 2026, 8:40 p.m.