Triple

T30196114
Position Surface form Disambiguated ID Type / Status
Subject Alt-Hohenschönhausen E767632 entity
Predicate hasLandmark P105 FINISHED
Object Hohenschönhausen Castle
Hohenschönhausen Castle is a historic manor house and former noble residence in Berlin’s Alt-Hohenschönhausen district, now used as a cultural and event venue.
E1911369 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: Hohenschönhausen Castle | Statement: [Alt-Hohenschönhausen, hasLandmark, Hohenschönhausen Castle]
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: Hohenschönhausen Castle
Triple: [Alt-Hohenschönhausen, hasLandmark, Hohenschönhausen Castle]
Generated description
Hohenschönhausen Castle is a historic manor house and former noble residence in Berlin’s Alt-Hohenschönhausen district, now used as a cultural and event venue.

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_69f2247db1108190835c0727c97637c3 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67f879cd88190989f5c86990caf3f completed May 2, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a277bfec8848190ab028b8b53b72ee5 completed June 9, 2026, 2:35 a.m.
NEDg Description generation batch_6a277c81407c8190a00cacd6c03b6822 completed June 9, 2026, 2:37 a.m.
NED2 Entity disambiguation (via description) batch_6a277cf84628819096ca30f4a50ed85f completed June 9, 2026, 2:39 a.m.
Created at: April 29, 2026, 7:29 p.m.