Triple

T9180547
Position Surface form Disambiguated ID Type / Status
Subject Bishopric of Bergheim E220314 entity
Predicate namedAfter P63 FINISHED
Object Bergheim E689941 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: Bergheim | Statement: [Bishopric of Bergheim, namedAfter, Bergheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bergheim
Context triple: [Bishopric of Bergheim, namedAfter, Bergheim]
  • A. Bergheim chosen
    Bergheim is a town in western Germany situated along the Erft River, known for its historical center and proximity to the Cologne region.
  • B. Bergheim
    Bergheim is a municipality in the Austrian state of Salzburg, located just north of the city of Salzburg and known for its suburban character and proximity to the regional capital.
  • C. Marlenheim
    Marlenheim is a commune in northeastern France’s Alsace region, known as a historic wine-producing village and gateway to the area’s renowned vineyards and scenic countryside.
  • D. Hademstorf
    Hademstorf is a small municipality in Lower Saxony, Germany, situated in the Heidekreis district.
  • E. Betzdorf
    Betzdorf is a commune in eastern Luxembourg known for its residential areas, railway facilities, and the presence of Betzdorf Castle.
  • 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_69ca83e589948190ac9907819db11ddf completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccc251da448190a5c7f684dac15a84 completed April 1, 2026, 6:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2696450e4819086d5aac368127e5f completed April 5, 2026, 1:53 p.m.
Created at: March 30, 2026, 7:23 p.m.