Triple

T19893571
Position Surface form Disambiguated ID Type / Status
Subject Bernhard I, Lord of Lippe E478091 entity
Predicate title P38 FINISHED
Object Lord of Lippe 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: Lord of Lippe | Statement: [Bernhard I, Lord of Lippe, title, Lord of Lippe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lord of Lippe
Context triple: [Bernhard I, Lord of Lippe, title, Lord of Lippe]
  • A. Lord of Lippe chosen
    The Lord of Lippe was the medieval noble title held by the rulers of the small German territory of Lippe before it was elevated to a county.
  • B. Herzog von Oels
    Herzog von Oels was the German ducal title borne by the Piast rulers of the Silesian duchy centered on Oleśnica (Oels) in present-day Poland.
  • C. Fürst zu Waldeck
    Fürst zu Waldeck was the princely title of the sovereign ruler of the small German principality of Waldeck within the Holy Roman Empire and later the German Confederation.
  • D. King of Münster
    The King of Münster was the theocratic monarch of the radical 16th-century Anabaptist regime that briefly ruled the German city of Münster during the Reformation.
  • E. Graf zu Waldeck
    Graf zu Waldeck is a noble title historically borne by members of the German princely House of Waldeck.
  • 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6590f9eb481909104a6a404c5c331 completed April 20, 2026, 4:49 p.m.
Created at: April 10, 2026, 1:52 p.m.