Triple

T22317092
Position Surface form Disambiguated ID Type / Status
Subject Gallus E551673 entity
Predicate borderedBy P224 FINISHED
Object Griesheim 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: Griesheim | Statement: [Gallus, borderedBy, Griesheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Griesheim
Context triple: [Gallus, borderedBy, Griesheim]
  • A. Griesheim chosen
    Griesheim is a town in the German state of Hesse, located near the city of Darmstadt and known for its residential character and local industry.
  • B. Sulzheim
    Sulzheim is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • C. Eschersheim
    Eschersheim is a district of Frankfurt am Main in Germany, historically notable as the birthplace of chemist Friedrich Wöhler.
  • D. Gerlachsheim
    Gerlachsheim is a district of the town Lauda-Königshofen in the Main-Tauber-Kreis region of Baden-Württemberg, Germany.
  • E. Ringelheim
    Ringelheim is a historic locality in present-day Germany, known as the birthplace of the early medieval noblewoman and later saint Matilda of Ringelheim.
  • 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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157535eb48190adbefbb619cb5fcd completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.