Triple

T32856282
Position Surface form Disambiguated ID Type / Status
Subject Volgograd urban transport network E840383 entity
Predicate servesLandmark P7126 FINISHED
Object Dzerzhinsky District
Dzerzhinsky District is an administrative district within the city of Volgograd, Russia, known as one of its urban residential and commercial areas.
E2288099 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: Dzerzhinsky District | Statement: [Volgograd urban transport network, servesLandmark, Dzerzhinsky District]
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: Dzerzhinsky District
Triple: [Volgograd urban transport network, servesLandmark, Dzerzhinsky District]
Generated description
Dzerzhinsky District is an administrative district within the city of Volgograd, Russia, known as one of its urban residential and commercial areas.

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_69f349412c78819084459850e11d29f7 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6ce7e58108190a3f06d0b27c608bd completed May 3, 2026, 4:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5a64511ca081909f7fa8ca57ae32f0 completed July 17, 2026, 5:20 p.m.
NEDg Description generation batch_6a5a650e016c8190ba6988a1555f1fc8 completed July 17, 2026, 5:23 p.m.
NED2 Entity disambiguation (via description) batch_6a5a65d62410819087d99143cb5288a8 completed July 17, 2026, 5:26 p.m.
Created at: May 1, 2026, 1:17 a.m.