Triple

T36614099
Position Surface form Disambiguated ID Type / Status
Subject Viereth-Trunstadt E903554 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Bischberg
Bischberg is a municipality in the Upper Franconia region of Bavaria, Germany, located near the city of Bamberg at the confluence of the Regnitz and Main rivers.
E2199838 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: Bischberg | Statement: [Viereth-Trunstadt, hasNeighbouringMunicipality, Bischberg]
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: Bischberg
Triple: [Viereth-Trunstadt, hasNeighbouringMunicipality, Bischberg]
Generated description
Bischberg is a municipality in the Upper Franconia region of Bavaria, Germany, located near the city of Bamberg at the confluence of the Regnitz and Main rivers.

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_69f76e6960e4819092047756ceb9a17e completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c47f4f1881908e584bfd65be7929 completed May 3, 2026, 9:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3d17852ae08190a60699f0066a8514 completed June 25, 2026, 11:56 a.m.
NEDg Description generation batch_6a3d1828cb4081908806cc837aac45a8 completed June 25, 2026, 11:59 a.m.
NED2 Entity disambiguation (via description) batch_6a3dcecff9488190829ea20f5bdde66c completed June 26, 2026, 12:58 a.m.
Created at: May 3, 2026, 4:11 p.m.