Triple

T19325624
Position Surface form Disambiguated ID Type / Status
Subject Schwäbisch Hall (district) E483339 entity
Predicate contains P35 FINISHED
Object Gaildorf 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: Gaildorf | Statement: [Schwäbisch Hall (district), contains, Gaildorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gaildorf
Context triple: [Schwäbisch Hall (district), contains, Gaildorf]
  • A. Gaildorf chosen
    Gaildorf is a small town in the German state of Baden-Württemberg, situated in the Kocher River valley and known for its historic center and surrounding rural landscape.
  • B. Fritzdorf
    Fritzdorf is a village in the municipality of Wachtberg in North Rhine-Westphalia, Germany.
  • C. Reundorf
    Reundorf is a village-level subdivision of the town of Lichtenfels in the Upper Franconia region of Bavaria, Germany.
  • D. Osterburg
    Osterburg is a small town in the German state of Saxony-Anhalt, known for its historic architecture and rural surroundings.
  • E. Friedeberg
    Friedeberg is a historic town that served as one of the principal urban centers of the Neumark region in former Brandenburg, now located in western Poland.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e60d8bb28c81909b3a3bbb96b69b4f completed April 20, 2026, 11:27 a.m.
Created at: April 10, 2026, 1:33 p.m.