Triple

T18468145
Position Surface form Disambiguated ID Type / Status
Subject Maria of Jülich-Berg E451218 entity
Predicate placeOfDeath P21 FINISHED
Object Rheinberg 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: Rheinberg | Statement: [Maria of Jülich-Berg, placeOfDeath, Rheinberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rheinberg
Context triple: [Maria of Jülich-Berg, placeOfDeath, Rheinberg]
  • A. Rheinberg chosen
    Rheinberg is a historic town in western Germany, situated on the Lower Rhine and known for its medieval architecture and role in various European military conflicts.
  • B. Rhenen
    Rhenen is a historic town and municipality in the central Netherlands, known for its scenic location along the Rhine and landmarks such as the Cunera Church and Ouwehands Zoo.
  • 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. Schippenbeil
    Schippenbeil is the former German name for the town now known as Sępopol in northeastern Poland.
  • E. Emmerich am Rhein
    Emmerich am Rhein is a German town on the Rhine River near the Dutch border, known for its historic center and prominent Rhine bridge.
  • 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_69d8d38465a0819099b9b42d2a662ac1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e52a857b1481908ebfcf832c83376f completed April 19, 2026, 7:18 p.m.
Created at: April 10, 2026, 11:34 a.m.