Triple

T14561900
Position Surface form Disambiguated ID Type / Status
Subject Polyxena of Hesse-Rotenburg E341687 entity
Predicate placeOfBirth P1 FINISHED
Object Langenschwalbach E811115 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: Langenschwalbach | Statement: [Polyxena of Hesse-Rotenburg, placeOfBirth, Langenschwalbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langenschwalbach
Context triple: [Polyxena of Hesse-Rotenburg, placeOfBirth, Langenschwalbach]
  • A. Langenschwalbach chosen
    Langenschwalbach is the historical name of Bad Schwalbach, a spa town in the Taunus region of Hesse, Germany, known for its mineral springs and health resorts.
  • B. Gernsbach
    Gernsbach is a historic town in southwestern Germany’s Black Forest region, known for its medieval old town and picturesque setting along the Murg River.
  • C. Emsbach
    Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
  • D. Langenau
    Langenau is a small town in the Alb-Donau district of Baden-Württemberg in southern Germany, known for its historic center and proximity to the Swabian Jura.
  • E. Wörsbach
    Wörsbach is a small river in Hesse, Germany, that forms part of the local drainage system for the Idsteiner Senke basin.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb389d0f48190a1d9d69456d1cbe1 completed April 14, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d379bc881908b7954c633787165 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 1:23 a.m.