Triple

T12454436
Position Surface form Disambiguated ID Type / Status
Subject S1 line E297619 entity
Predicate passesThrough P225 FINISHED
Object Hochheim am Main E794407 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: Hochheim am Main | Statement: [S1 line, passesThrough, Hochheim am Main]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hochheim am Main
Context triple: [S1 line, passesThrough, Hochheim am Main]
  • A. Hochheim am Main chosen
    Hochheim am Main is a historic wine-producing town in the German state of Hesse, renowned for its Riesling wines and scenic location along the Main River near the Rheingau region.
  • B. Hochstadt am Main
    Hochstadt am Main is a small municipality in the Upper Franconia region of Bavaria, Germany, situated along the Main River.
  • C. Höchheim
    Höchheim is a small municipality in the Rhön-Grabfeld district of northern Bavaria, Germany.
  • D. Höchstadt an der Aisch
    Höchstadt an der Aisch is a small Bavarian town in Germany known for its historic center and location in the Aisch river valley.
  • E. Oberhöchstadt
    Oberhöchstadt is a district of the town of Kronberg im Taunus in Hesse, Germany, known for its residential character within the Taunus region.
  • 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_69d6ada166c48190b902972cd2408fa3 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94da0b5988190b9df26dd3bb87337 completed April 10, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f66859c0448190980c5e490cc41118 completed May 2, 2026, 9:10 p.m.
Created at: April 8, 2026, 9:56 p.m.