Triple

T6994468
Position Surface form Disambiguated ID Type / Status
Subject Heinrich Eberbach E162173 entity
Predicate familyName P18 FINISHED
Object Eberbach E390774 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: Eberbach | Statement: [Heinrich Eberbach, familyName, Eberbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eberbach
Context triple: [Heinrich Eberbach, familyName, Eberbach]
  • A. Eberbach chosen
    Eberbach is a small historic town in southwestern Germany, known for its picturesque location in the Odenwald hills along the Neckar River.
  • B. Euerbach
    Euerbach is a small municipality in the Schweinfurt district of northern Bavaria, Germany, known for its rural character and Franconian cultural heritage.
  • C. Emsbach
    Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
  • D. Schambach
    Schambach is a small river in Bavaria, Germany, that flows into the Altmühl as one of its tributaries.
  • E. Gernsbach
    Gernsbach is a historic town in southwestern Germany’s Black Forest region, known for its medieval old town and picturesque setting along the Murg River.
  • 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_69c68856d7808190ab33ee914640281b completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbeaa88c8190a49f8504c1793e1f completed March 27, 2026, 7:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e50580c08190aa737043ad7520a0 completed March 28, 2026, 2:26 p.m.
Created at: March 27, 2026, 2:32 p.m.