Triple

T34072659
Position Surface form Disambiguated ID Type / Status
Subject County of Hohenzollern E873814 entity
Predicate hasDynastyBranch P13166 FINISHED
Object Swabian branch of the House of Hohenzollern 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: Swabian branch of the House of Hohenzollern | Statement: [County of Hohenzollern, hasDynastyBranch, Swabian branch of the House of Hohenzollern]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDynastyBranch
Context triple: [County of Hohenzollern, hasDynastyBranch, Swabian branch of the House of Hohenzollern]
  • A. dynasticBranch chosen
    Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
  • B. isDynastic
    Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
  • C. hasDynast
    Indicates that an entity is associated with or ruled by a particular dynasty.
  • D. hasDynasticConnections
    Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
  • E. hasBranchOfImperialFamily
    Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
  • 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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70fb4f18c819099ef6d9177b7d205 completed May 3, 2026, 9:04 a.m.
PD Predicate disambiguation batch_69f70f3a54d481909ba6bdda3647b761 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:52 a.m.