Triple

T31955249
Position Surface form Disambiguated ID Type / Status
Subject Yekaterinburg Metro E815886 entity
Predicate hasStation P35 FINISHED
Object Ploshchad 1905 Goda
Ploshchad 1905 Goda is a central metro station in Yekaterinburg, Russia, named after the nearby historic square commemorating the events of the 1905 Revolution.
E1985212 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: Ploshchad 1905 Goda | Statement: [Yekaterinburg Metro, hasStation, Ploshchad 1905 Goda]
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: Ploshchad 1905 Goda
Triple: [Yekaterinburg Metro, hasStation, Ploshchad 1905 Goda]
Generated description
Ploshchad 1905 Goda is a central metro station in Yekaterinburg, Russia, named after the nearby historic square commemorating the events of the 1905 Revolution.

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_69f348f4ec708190abbb2a7c3ed58844 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b2ae50e08190b0756dfe533618ea completed May 3, 2026, 2:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e8a4ff3cc8190b085ba11c656c7cf completed June 14, 2026, 11:02 a.m.
NEDg Description generation batch_6a2e8af50dc08190bbc5f3e04528b335 completed June 14, 2026, 11:05 a.m.
NED2 Entity disambiguation (via description) batch_6a2ea6a967dc8190af1d4e84ed34013b completed June 14, 2026, 1:03 p.m.
Created at: May 1, 2026, 12:08 a.m.