Triple

T30701648
Position Surface form Disambiguated ID Type / Status
Subject Tempelhof Town Hall E781625 entity
Predicate partOf P40 FINISHED
Object Tempelhof district
Tempelhof district is a locality in southern Berlin, Germany, known for its historic airport-turned-park and its mix of residential neighborhoods and civic buildings.
E34860 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: Tempelhof district | Statement: [Tempelhof Town Hall, partOf, Tempelhof district]
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: Tempelhof district
Triple: [Tempelhof Town Hall, partOf, Tempelhof district]
Generated description
Tempelhof district is a locality in southern Berlin, Germany, known for its historic airport-turned-park and its mix of residential neighborhoods and civic buildings.

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_69f224abfcf081909492e64d3cc35262 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68bdf2b3c81909578a19e0190e45d completed May 2, 2026, 11:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a36a0086eb48190aa167bf69ac44234 completed June 20, 2026, 2:13 p.m.
NEDg Description generation batch_6a36a06636648190bbbcc950efbf84ea completed June 20, 2026, 2:15 p.m.
NED2 Entity disambiguation (via description) batch_6a36a0f92ea88190b78f03deb61f869f completed June 20, 2026, 2:17 p.m.
Created at: April 29, 2026, 8:34 p.m.