Triple

T38523995
Position Surface form Disambiguated ID Type / Status
Subject Lichtenfels (Waldeck-Frankenberg) E922576 entity
Predicate formedByMergerOf P77 FINISHED
Object Goddelsheim
Goddelsheim is a former independent locality in the Waldeck-Frankenberg district of Hesse, Germany, now part of the town of Lichtenfels.
E2285625 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: Goddelsheim | Statement: [Lichtenfels (Waldeck-Frankenberg), formedByMergerOf, Goddelsheim]
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: Goddelsheim
Triple: [Lichtenfels (Waldeck-Frankenberg), formedByMergerOf, Goddelsheim]
Generated description
Goddelsheim is a former independent locality in the Waldeck-Frankenberg district of Hesse, Germany, now part of the town of Lichtenfels.

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_69f76ea5f5588190bd0b28c82e975640 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcd2b3fac481908f3481cb08a62db8 completed May 7, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4602ab1f288190bac44855170f1ada completed July 2, 2026, 6:18 a.m.
NEDg Description generation batch_6a46037bb6d8819095195039f9501d34 completed July 2, 2026, 6:21 a.m.
NED2 Entity disambiguation (via description) batch_6a4603eccccc8190930997e8b606002a completed July 2, 2026, 6:23 a.m.
Created at: May 3, 2026, 4:32 p.m.