Triple

T33717289
Position Surface form Disambiguated ID Type / Status
Subject Tiefenbach E863910 entity
Predicate hasMunicipalParent P33889 FINISHED
Object town of Braunfels
The town of Braunfels is a historic spa and castle town in the Lahn-Dill district of Hesse, Germany, known for its medieval old town and hilltop Braunfels Castle.
E2062781 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: town of Braunfels | Statement: [Tiefenbach, hasMunicipalParent, town of Braunfels]
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: town of Braunfels
Triple: [Tiefenbach, hasMunicipalParent, town of Braunfels]
Generated description
The town of Braunfels is a historic spa and castle town in the Lahn-Dill district of Hesse, Germany, known for its medieval old town and hilltop Braunfels Castle.

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_69f34989871c81908682e22a2fe4b829 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fae5adbc8190ad5c1576ab1b0687 completed May 3, 2026, 7:36 a.m.
NED1 Entity disambiguation (via context triple) batch_6a363cab69b8819098e9083909444f94 completed June 20, 2026, 7:09 a.m.
NEDg Description generation batch_6a36466a52208190b24580693192f0e2 completed June 20, 2026, 7:51 a.m.
NED2 Entity disambiguation (via description) batch_6a36478c793c8190a48758a42ac2337d completed June 20, 2026, 7:55 a.m.
Created at: May 1, 2026, 1:44 a.m.