Triple

T32696628
Position Surface form Disambiguated ID Type / Status
Subject Dresden tram network E836024 entity
Predicate hasStop P17789 FINISHED
Object Kleinzschachwitz
Kleinzschachwitz is a district of Dresden, Germany, located along the Elbe River and known for its residential character and proximity to the historic Pillnitz area.
E2117748 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: Kleinzschachwitz | Statement: [Dresden tram network, hasStop, Kleinzschachwitz]
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: Kleinzschachwitz
Triple: [Dresden tram network, hasStop, Kleinzschachwitz]
Generated description
Kleinzschachwitz is a district of Dresden, Germany, located along the Elbe River and known for its residential character and proximity to the historic Pillnitz area.

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_69f3493323288190a4e88251035fe96e completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6c84a7a9c819087a695a3ce1929ed completed May 3, 2026, 4 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3786b3c5ac8190b371ef82ae6e1de1 completed June 21, 2026, 6:37 a.m.
NEDg Description generation batch_6a378ff276908190970b80e1ff5dc26b completed June 21, 2026, 7:17 a.m.
NED2 Entity disambiguation (via description) batch_6a37909317608190ab11d7b9d5175762 completed June 21, 2026, 7:19 a.m.
Created at: May 1, 2026, 1:10 a.m.