Triple

T18560422
Position Surface form Disambiguated ID Type / Status
Subject Ziegenhain E453622 entity
Predicate locatedIn P40 FINISHED
Object north Hesse 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: north Hesse | Statement: [Ziegenhain, locatedIn, north Hesse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: north Hesse
Context triple: [Ziegenhain, locatedIn, north Hesse]
  • A. western Hesse
    Western Hesse is a region in the German state of Hesse characterized by its location along the Rhine-Main area and its mix of industrial cities and rural landscapes.
  • B. South Hesse
    South Hesse is a region in the southern part of the German state of Hesse that includes major urban and economic centers such as Darmstadt and the Rhine-Main area.
  • C. Upper Hesse
    Upper Hesse was a historical region in central Germany that formed the northern, upland part of the Landgraviate of Hesse-Darmstadt.
  • D. Nordhessen chosen
    Nordhessen is a region in northern Hesse, Germany, centered around the city of Kassel and known for its forests, low mountain ranges, and cultural-historical significance.
  • E. Northern Hesse region
    The Northern Hesse region is a historical area in central Germany that once formed part of the territorial domain of the Prince of Waldeck.
  • 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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e538098a148190b0fc7098ce3c62fd completed April 19, 2026, 8:16 p.m.
Created at: April 10, 2026, 11:42 a.m.