Triple

T31886449
Position Surface form Disambiguated ID Type / Status
Subject Hanover-Mitte E814019 entity
Predicate contains P35 FINISHED
Object Leibnizhaus Hanover
Leibnizhaus Hanover is a reconstructed Renaissance-style townhouse in Hanover, Germany, named after philosopher Gottfried Wilhelm Leibniz and used today as a cultural and event venue.
E1982515 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: Leibnizhaus Hanover | Statement: [Hanover-Mitte, contains, Leibnizhaus Hanover]
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: Leibnizhaus Hanover
Triple: [Hanover-Mitte, contains, Leibnizhaus Hanover]
Generated description
Leibnizhaus Hanover is a reconstructed Renaissance-style townhouse in Hanover, Germany, named after philosopher Gottfried Wilhelm Leibniz and used today 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_69f348ef817481908440e2250319bcc8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b0db6b248190bf48c8088d41345d completed May 3, 2026, 2:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e7fe591bc819098ecfe852e88149e completed June 14, 2026, 10:18 a.m.
NEDg Description generation batch_6a2e80bfc09c81908b0f21d5dc3629e9 completed June 14, 2026, 10:21 a.m.
NED2 Entity disambiguation (via description) batch_6a2e81c63b8081909989e5e18ce19954 completed June 14, 2026, 10:26 a.m.
Created at: April 30, 2026, 11:57 p.m.