Triple

T20838145
Position Surface form Disambiguated ID Type / Status
Subject Appenweier E513015 entity
Predicate hasDemonym P191 FINISHED
Object Appenweierer 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: Appenweierer | Statement: [Appenweier, hasDemonym, Appenweierer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Appenweierer
Context triple: [Appenweier, hasDemonym, Appenweierer]
  • A. Appenweier chosen
    Appenweier is a municipality in southwestern Germany’s Baden-Württemberg region, situated within the Ortenau district near the Rhine and the French border.
  • B. Eifgenbach
    Eifgenbach is a small river in North Rhine-Westphalia, Germany, that flows through the Bergisches Land region before joining the Wupper.
  • C. Oberägeri
    Oberägeri is a Swiss municipality in the canton of Zug, known for its scenic location by Lake Ägeri and surrounding pre-Alpine landscapes.
  • D. Sulzenauferner
    Sulzenauferner is a glacier in the Stubai Alps of Tyrol, Austria, known for its high-alpine scenery and popular mountaineering routes.
  • E. Feldbach
    Feldbach is a small town in southeastern Austria known for its historic center and location in the Styrian volcanic region.
  • 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_69e0b4cf62a88190bbf92351e9e57259 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c32928788190be8ca57923eefd7e completed April 21, 2026, 12:22 a.m.
Created at: April 16, 2026, 12:42 p.m.