Triple

T16561012
Position Surface form Disambiguated ID Type / Status
Subject Kraichgau E402336 entity
Predicate contains P35 FINISHED
Object Walldorf E711021 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: Walldorf | Statement: [Kraichgau, contains, Walldorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Walldorf
Context triple: [Kraichgau, contains, Walldorf]
  • A. Walldorf chosen
    Walldorf is a town in southwestern Germany best known as the headquarters of software giant SAP and for its strong economic base in the technology sector.
  • B. Puchheim
    Puchheim is a small town in Upper Bavaria, Germany, situated near Munich and known as a residential and commuter community.
  • C. Weinheim
    Weinheim is a historic town in southwestern Germany, known for its picturesque old town, twin castles, and location on the Bergstraße at the edge of the Odenwald.
  • D. Pulheim
    Pulheim is a town in western Germany’s North Rhine-Westphalia, situated just northwest of Cologne within the broader Cologne/Bonn urban area.
  • E. Bensheim
    Bensheim is a historic town in southern Hesse, Germany, known for its wine-growing tradition and picturesque location on the Bergstraße at the edge of the Odenwald.
  • 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_69d8838648088190acf97ef11fc3f61b completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3576d88288190b33543bea4706a36 completed April 18, 2026, 10:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006eddb01081908e7ab59264199e15 completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:15 a.m.