Triple

T7381414
Position Surface form Disambiguated ID Type / Status
Subject Prince of Lippe E170260 entity
Predicate dynasticBranch P13166 FINISHED
Object Lippe-Detmold E269423 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-Detmold | Statement: [Prince of Lippe, dynasticBranch, Lippe-Detmold]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lippe-Detmold
Context triple: [Prince of Lippe, dynasticBranch, Lippe-Detmold]
  • A. Lippe-Biesterfeld
    Lippe-Biesterfeld is a cadet branch of the German princely House of Lippe, historically associated with several minor German nobles and later with the Dutch royal family.
  • B. Detmold chosen
    Detmold is a historic town in northwestern Germany that served as the capital and residence city of the former Principality of Lippe.
  • C. Meppen
    Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
  • D. Bentheim
    Bentheim is a historical county in Lower Saxony, Germany, known for its Reformed Protestant heritage and the former County of Bentheim.
  • E. Lemgo
    Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
  • 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_69c68a5d0ed08190b6d361e68f813330 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1c7b5bc81908afa2bf39159979b completed March 27, 2026, 9:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802db77988190aacc4e2f9cbb0bb3 completed March 28, 2026, 4:33 p.m.
Created at: March 27, 2026, 3:08 p.m.