Triple

T19335261
Position Surface form Disambiguated ID Type / Status
Subject Giessen district E483605 entity
Predicate contains P35 FINISHED
Object Heuchelheim 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: Heuchelheim | Statement: [Giessen district, contains, Heuchelheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heuchelheim
Context triple: [Giessen district, contains, Heuchelheim]
  • A. Harzheim
    Harzheim is a village in the town of Mechernich in North Rhine-Westphalia, Germany.
  • B. Marlenheim
    Marlenheim is a commune in northeastern France’s Alsace region, known as a historic wine-producing village and gateway to the area’s renowned vineyards and scenic countryside.
  • C. Pohlheim chosen
    Pohlheim is a small town in the German state of Hesse, located near the city of Gießen in central Germany.
  • D. Heuckewalde
    Heuckewalde is a small municipality in the German state of Saxony-Anhalt that forms part of the broader Leipzig metropolitan region.
  • E. Hecklingen
    Hecklingen is a small town in the Salzlandkreis district of the German state of Saxony-Anhalt, known for its historic architecture and rural character.
  • 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_69e61644b80c819080f9bca086424a36 completed April 20, 2026, 12:04 p.m.
Created at: April 10, 2026, 1:33 p.m.