Triple

T17822276
Position Surface form Disambiguated ID Type / Status
Subject Jagst E445014 entity
Predicate parallelTo P1868 FINISHED
Object Kocher 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: Kocher | Statement: [Jagst, parallelTo, Kocher]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kocher
Context triple: [Jagst, parallelTo, Kocher]
  • A. Kocher chosen
    The Kocher is a river in the German state of Baden-Württemberg that flows through towns such as Aalen and Schwäbisch Hall before joining the Neckar.
  • B. Kocher
    Kocher is a Swiss surname most notably associated with Nobel Prize–winning surgeon Emil Theodor Kocher.
  • C. Guerin
    Guerin is a surname of French origin borne by various notable individuals across fields such as arts, sports, and public life.
  • D. Kienbaum
    Kienbaum is a small village in the municipality of Grünheide (Mark) in Brandenburg, Germany, known in part for its nearby national Olympic training center.
  • E. Meyerhof
    Meyerhof is a surname of German origin, notably borne by biochemist Otto Fritz Meyerhof, a Nobel laureate recognized for his work on muscle metabolism.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48911b660819097fc7ea94665a02a completed April 19, 2026, 7:49 a.m.
Created at: April 10, 2026, 10:15 a.m.