Triple

T37234062
Position Surface form Disambiguated ID Type / Status
Subject Театральная площадь, Москва E923519 entity
Predicate hasNearby P350 FINISHED
Object Неглинная улица
Неглинная улица — это историческая улица в центре Москвы, проходящая рядом с Театральной площадью и ведущая к ключевым культурным и административным объектам города.
E2288543 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: [Театральная площадь, Москва, hasNearby, Неглинная улица]
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: [Театральная площадь, Москва, hasNearby, Неглинная улица]
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_69f76ea9fee88190a589f661d95a7189 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb36ce25cc8190b56c4e5520bac0b9 completed May 6, 2026, 12:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5a99d19694819099a69828f089631e completed July 17, 2026, 9:08 p.m.
NEDg Description generation batch_6a5a9a34f7c8819094ad056a5782f41b completed July 17, 2026, 9:10 p.m.
NED2 Entity disambiguation (via description) batch_6a5a9aab6cdc81909ce1bf98dfb69a95 completed July 17, 2026, 9:12 p.m.
Created at: May 3, 2026, 4:15 p.m.