Triple

T2046933
Position Surface form Disambiguated ID Type / Status
Subject Mossenberg-Wöhren E45473 entity
Predicate hasRegionalContext P285 FINISHED
Object Lippe E138916 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: Lippe | Statement: [Mossenberg-Wöhren, hasRegionalContext, Lippe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lippe
Context triple: [Mossenberg-Wöhren, hasRegionalContext, Lippe]
  • A. Lippe
    The Lippe is a river in western Germany that flows through North Rhine-Westphalia and is a right-bank tributary of the Rhine.
  • B. Lippe chosen
    Lippe is a historical region in northwestern Germany that once formed a small principality and later a Free State within the German Reich.
  • C. Rheine
    Rheine is a German city in the state of North Rhine-Westphalia, known for its historical town center and location along the River Ems.
  • D. Erft River
    The Erft River is a tributary of the Rhine in western Germany, flowing through North Rhine-Westphalia and known for passing historic towns and former mining areas before joining the Rhine near Neuss.
  • E. Roer
    The Roer is a river in Western Europe that flows through parts of Belgium, Germany, and the Netherlands before joining the Meuse.
  • 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_69a8891948208190ab7898da21824c77 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb973a51881908c2c1e633daa3cb4 completed March 7, 2026, 5:36 a.m.
NED1 Entity disambiguation (via context triple) batch_69afe86f11108190a1987c1cee133d56 completed March 10, 2026, 9:46 a.m.
Created at: March 4, 2026, 7:39 p.m.