Triple

T31628826
Position Surface form Disambiguated ID Type / Status
Subject Wehrheim E807101 entity
Predicate hasSubdivision P747 FINISHED
Object Obernhain
Obernhain is a village and district of the municipality of Wehrheim in the Hochtaunus region of Hesse, Germany.
E1976283 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: Obernhain | Statement: [Wehrheim, hasSubdivision, Obernhain]
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: Obernhain
Triple: [Wehrheim, hasSubdivision, Obernhain]
Generated description
Obernhain is a village and district of the municipality of Wehrheim in the Hochtaunus region of Hesse, Germany.

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_69f348d7883c8190b6c13ab92b7ef076 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a8e303148190b0f8959045db3073 completed May 3, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b945faf488190bc26e1f4d8276168 completed June 12, 2026, 5:08 a.m.
NEDg Description generation batch_6a2b982b0c0c81909ff54435fa3d143d completed June 12, 2026, 5:24 a.m.
NED2 Entity disambiguation (via description) batch_6a2b98821b9081909337a20e95dcd97a completed June 12, 2026, 5:26 a.m.
Created at: April 30, 2026, 10:44 p.m.