Triple

T26703374
Position Surface form Disambiguated ID Type / Status
Subject Biesterfeld E673219 entity
Predicate nobleBranchOrigin P98292 FINISHED
Object Lippe-Biesterfeld line of the House 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: Lippe-Biesterfeld line of the House of Lippe | Statement: [Biesterfeld, nobleBranchOrigin, Lippe-Biesterfeld line of the House of Lippe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nobleBranchOrigin
Context triple: [Biesterfeld, nobleBranchOrigin, Lippe-Biesterfeld line of the House of Lippe]
  • A. producedNobleBranch chosen
    Indicates that one entity gave rise to or resulted in the formation of a particular noble family line or branch.
  • B. hasNobleHouseOrigin
    Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
  • C. dynasticOrigin
    Indicates the historical dynasty or ruling family from which an entity originates or descends.
  • D. foundingAncestor
    Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
  • E. notableFamilyOrigin
    Indicates that an entity is recognized for originating from, or being notably associated with, a particular family background or lineage.
  • F. None of above.

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_69eecda2b49c8190a6c481cfc4c07954 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f61a17a7788190946f7e32d63cd43f completed May 2, 2026, 3:36 p.m.
PD Predicate disambiguation batch_69f611ab768c8190b1849c15a3e59dda completed May 2, 2026, 3 p.m.
Created at: April 27, 2026, 3:32 a.m.