Triple

T20341391
Position Surface form Disambiguated ID Type / Status
Subject Wolhusen E495747 entity
Predicate hasSettlementPart P8239 FINISHED
Object Wolhusen Dorf NE NERFINISHED

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: Wolhusen Dorf | Statement: [Wolhusen, hasSettlementPart, Wolhusen Dorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wolhusen Dorf
Context triple: [Wolhusen, hasSettlementPart, Wolhusen Dorf]
  • A. Wolhusen chosen
    Wolhusen is a municipality in the canton of Lucerne in central Switzerland, known as a regional transport hub and gateway to the Entlebuch region.
  • B. Antdorf
    Antdorf is a small rural municipality in Upper Bavaria, Germany, known for its traditional Bavarian character and scenic Alpine foothill landscape.
  • C. Hundwil
    Hundwil is a small Swiss municipality known for its rural character and traditional Appenzell culture in northeastern Switzerland.
  • D. Wüllen
    Wüllen is a district of the town of Ahaus in North Rhine-Westphalia, Germany, known for its rural character within the Münsterland region.
  • E. Neuenhof
    Neuenhof is a municipality in the canton of Aargau in northern Switzerland, situated in the Limmat Valley near the city of Baden.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4a3320881909495ae8bc30bc2dc completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67835f6e881908834dda06cf66c50 completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:23 a.m.