Triple

T29317478
Position Surface form Disambiguated ID Type / Status
Subject Spremberger Turm E743417 entity
Predicate locatedIn P40 FINISHED
Object Spremberger Straße
Spremberger Straße is a central street in Cottbus, Germany, known for its historic architecture, shopping areas, and the prominent Spremberger Turm city gate.
E1999711 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: Spremberger Straße | Statement: [Spremberger Turm, locatedIn, Spremberger Straße]
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: Spremberger Straße
Triple: [Spremberger Turm, locatedIn, Spremberger Straße]
Generated description
Spremberger Straße is a central street in Cottbus, Germany, known for its historic architecture, shopping areas, and the prominent Spremberger Turm city gate.

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_69f0912502c8819087d9e8398ee991a8 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f665ed51ac8190a2fb442294349535 completed May 2, 2026, 9 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2f46ab264c8190971e9be54df04f95 completed June 15, 2026, 12:26 a.m.
NEDg Description generation batch_6a2f48ed53d081909c9b26a5303fbc54 completed June 15, 2026, 12:35 a.m.
NED2 Entity disambiguation (via description) batch_6a2f4940fc2481909cd539b134f08560 completed June 15, 2026, 12:37 a.m.
Created at: April 28, 2026, 1:20 p.m.