Triple

T7740404
Position Surface form Disambiguated ID Type / Status
Subject Leopold II, Prince of Lippe E175491 entity
Predicate regionRuled P15936 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: [Leopold II, Prince of Lippe, regionRuled, Lippe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lippe
Context triple: [Leopold II, Prince of Lippe, regionRuled, Lippe]
  • A. 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.
  • B. Lippe
    The Lippe is a river in western Germany that flows through North Rhine-Westphalia and is a right-bank tributary of the Rhine.
  • 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. Wupper
    The Wupper is a river in North Rhine-Westphalia, Germany, known for flowing through the industrial city of Wuppertal and its surrounding region.
  • E. Emscher
    The Emscher is a river in Germany’s Ruhr industrial region, historically known for its heavy pollution and extensive canalization before major ecological restoration efforts.
  • 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_69c6995f9c60819092e386192bd63c6f completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7035cddb881908bdfc1bd7d6a64ad completed March 27, 2026, 10:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c988f902548190a3db57b4b6debf6c completed March 29, 2026, 8:18 p.m.
Created at: March 27, 2026, 4:07 p.m.