Triple

T29595171
Position Surface form Disambiguated ID Type / Status
Subject Moscow trolleybus network E754272 entity
Predicate notableDepot P207155 FINISHED
Object Baumansky trolleybus depot
Baumansky trolleybus depot is a major operational and maintenance facility that historically served a significant portion of Moscow’s trolleybus network.
E1879295 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: Baumansky trolleybus depot | Statement: [Moscow trolleybus network, notableDepot, Baumansky trolleybus depot]
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: Baumansky trolleybus depot
Triple: [Moscow trolleybus network, notableDepot, Baumansky trolleybus depot]
Generated description
Baumansky trolleybus depot is a major operational and maintenance facility that historically served a significant portion of Moscow’s trolleybus network.

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_69f0ef836ac88190bd809dc58b5ec907 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_6a03809725bc81909c8b61d72d72ca2b completed May 12, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a267ea62984819086d5706ecb87c485 completed June 8, 2026, 8:34 a.m.
NEDg Description generation batch_6a2682b72dc881909ee96a24b8cd2427 completed June 8, 2026, 8:52 a.m.
NED2 Entity disambiguation (via description) batch_6a2687c32e1c8190a9da1493708e831e completed June 8, 2026, 9:13 a.m.
Created at: April 28, 2026, 6:17 p.m.