Triple

T19325684
Position Surface form Disambiguated ID Type / Status
Subject Heilbronn (district) E483340 entity
Predicate contains P35 FINISHED
Object Lauffen am Neckar 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: Lauffen am Neckar | Statement: [Heilbronn (district), contains, Lauffen am Neckar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lauffen am Neckar
Context triple: [Heilbronn (district), contains, Lauffen am Neckar]
  • A. Lauffen am Neckar chosen
    Lauffen am Neckar is a small German town in the state of Baden-Württemberg, known for its wine production and picturesque location along the Neckar River.
  • B. Neckargemünd
    Neckargemünd is a small historic town in southwestern Germany, located at the confluence of the Neckar and Elsenz rivers near Heidelberg.
  • C. Herrlingen
    Herrlingen is a small village in the German state of Baden-Württemberg, historically noted as the place where Field Marshal Erwin Rommel spent his final days during World War II.
  • D. Gärtringen
    Gärtringen is a municipality in the German state of Baden-Württemberg, located southwest of Stuttgart.
  • E. Uffenheim
    Uffenheim is a small town in the Franconian region of northern Bavaria, Germany, known for its historic architecture and rural surroundings.
  • 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.