Triple

T21392667
Position Surface form Disambiguated ID Type / Status
Subject Wals-Siezenheim E527695 entity
Predicate hasSubdivision P747 FINISHED
Object Viehausen
Viehausen is a locality within the municipality of Wals-Siezenheim in the Austrian state of Salzburg.
E1540937 NE FINISHED

How this triple was built (4 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: Viehausen | Statement: [Wals-Siezenheim, hasSubdivision, Viehausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viehausen
Context triple: [Wals-Siezenheim, hasSubdivision, Viehausen]
  • A. Vellinghausen
    Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
  • B. Völlinghausen
    Völlinghausen is a village within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
  • C. Fahrenzhausen
    Fahrenzhausen is a municipality in Upper Bavaria, Germany, situated north of Munich along the Amper River.
  • D. Fischhausen
    Fischhausen was a historical town in East Prussia, notable as a residence and later the place of death of Prussian duke Albert Frederick.
  • E. Walzenhausen
    Walzenhausen is a Swiss village and municipality in the canton of Appenzell Ausserrhoden, known for its scenic location above Lake Constance and views over the Rhine Valley.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Viehausen
Triple: [Wals-Siezenheim, hasSubdivision, Viehausen]
Generated description
Viehausen is a locality within the municipality of Wals-Siezenheim in the Austrian state of Salzburg.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Viehausen
Target entity description: Viehausen is a locality within the municipality of Wals-Siezenheim in the Austrian state of Salzburg.
  • A. Vellinghausen
    Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
  • B. Völlinghausen
    Völlinghausen is a village within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
  • C. Fahrenzhausen
    Fahrenzhausen is a municipality in Upper Bavaria, Germany, situated north of Munich along the Amper River.
  • D. Fischhausen
    Fischhausen was a historical town in East Prussia, notable as a residence and later the place of death of Prussian duke Albert Frederick.
  • E. Walzenhausen
    Walzenhausen is a Swiss village and municipality in the canton of Appenzell Ausserrhoden, known for its scenic location above Lake Constance and views over the Rhine Valley.
  • F. None of above. chosen

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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b1159a888190aabb5c2a9268bd06 completed April 22, 2026, 11:29 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0b17c7198c8190b96754a4a0b317c1 completed May 18, 2026, 1:44 p.m.
NEDg Description generation batch_6a0b1ac642408190bb265ec0a797daf2 completed May 18, 2026, 1:57 p.m.
NED2 Entity disambiguation (via description) batch_6a0b1b28377c8190a6c28b470ee5f1f8 completed May 18, 2026, 1:59 p.m.
Created at: April 16, 2026, 5:13 p.m.