Triple

T20357653
Position Surface form Disambiguated ID Type / Status
Subject Beatus Rhenanus E496692 entity
Predicate birthPlace P1 FINISHED
Object Schlettstadt 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: Schlettstadt | Statement: [Beatus Rhenanus, birthPlace, Schlettstadt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schlettstadt
Context triple: [Beatus Rhenanus, birthPlace, Schlettstadt]
  • A. Schlettstadt chosen
    Schlettstadt, now known as Sélestat, is a historic town in the Alsace region of northeastern France noted for its medieval architecture and humanist heritage.
  • B. Schwalmstadt
    Schwalmstadt is a small town in the Schwalm-Eder district of northern Hesse, Germany, known for its historic half-timbered architecture and picturesque setting in the Schwalm River valley.
  • C. Ebermannstadt
    Ebermannstadt is a small historic town in northern Bavaria, Germany, known as a gateway to the scenic Franconian Switzerland region.
  • D. Gescher
    Gescher is a small town in western Germany’s Münsterland region, noted for its traditional bell foundries and rural character.
  • E. Sulzheim
    Sulzheim is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • 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_69e0b4a3f7f48190b37f354574028ca6 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67855c3a88190b88839a47d01184d completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:25 a.m.