Triple

T27768035
Position Surface form Disambiguated ID Type / Status
Subject Georgenkirchplatz E701656 entity
Predicate locatedNearStreet P8235 FINISHED
Object Dircksenstraße
Dircksenstraße is a central street in Berlin, Germany, running along the Stadtbahn viaduct and connecting several key squares and transport hubs in the city center.
E1898220 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: Dircksenstraße | Statement: [Georgenkirchplatz, locatedNearStreet, Dircksenstraß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: Dircksenstraße
Triple: [Georgenkirchplatz, locatedNearStreet, Dircksenstraße]
Generated description
Dircksenstraße is a central street in Berlin, Germany, running along the Stadtbahn viaduct and connecting several key squares and transport hubs in the city center.

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_69ef6a52fa708190934a32308d2c92dc completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f6379463488190b5d5cc8fa944f1fe completed May 2, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2742f1103c81908e414f1650fd09d5 completed June 8, 2026, 10:32 p.m.
NEDg Description generation batch_6a2743a08b1c81909d55cad20b10a018 completed June 8, 2026, 10:35 p.m.
NED2 Entity disambiguation (via description) batch_6a274408ddc081909598bd01287b5326 completed June 8, 2026, 10:36 p.m.
Created at: April 27, 2026, 4:32 p.m.