Triple

T22154057
Position Surface form Disambiguated ID Type / Status
Subject Montferland E547486 entity
Predicate hasBorderWith P224 FINISHED
Object Emmerich am Rhein 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: Emmerich am Rhein | Statement: [Montferland, hasBorderWith, Emmerich am Rhein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Emmerich am Rhein
Context triple: [Montferland, hasBorderWith, Emmerich am Rhein]
  • A. Emmerich am Rhein chosen
    Emmerich am Rhein is a German town on the Rhine River near the Dutch border, known for its historic center and prominent Rhine bridge.
  • B. Bingen am Rhein
    Bingen am Rhein is a historic town in Germany’s Rhineland-Palatinate, known as a gateway to the scenic Upper Middle Rhine Valley with its castles, vineyards, and river landscapes.
  • C. Rheinhausen
    Rheinhausen is a district of the German city of Duisburg, located on the western bank of the Rhine in North Rhine-Westphalia.
  • D. Monheim am Rhein
    Monheim am Rhein is a town in North Rhine-Westphalia, Germany, situated along the Rhine River and known for its strong local economy and family-friendly urban development.
  • E. Ramingstein
    Ramingstein is a small Austrian municipality in the Lungau region of Salzburg, known for its alpine setting and historic silver mining heritage.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f6d5b88190badee2e515a3b633 completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.