Triple

T34814738
Position Surface form Disambiguated ID Type / Status
Subject Henry Berengar E1003600 entity
Predicate instanceOf P0 FINISHED
Object 12th-century German noble C60426 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: 12th-century German noble
Context triple: [Henry Berengar, instanceOf, 12th-century German noble]
  • A. 9th-century German noble
    A 9th-century German noble was a member of the hereditary warrior aristocracy in the East Frankish realms, holding land and local authority in exchange for military service and loyalty to the Carolingian king or his successors.
  • B. 13th-century German noblewoman
    A 13th-century German noblewoman is an aristocratic woman of the Holy Roman Empire who managed estates, upheld family alliances through marriage, and navigated the social, legal, and religious structures of medieval German nobility.
  • C. 10th-century German noblewoman
    A 10th-century German noblewoman was an aristocratic woman in the fragmented realms of the early Holy Roman Empire, whose status, landholdings, and dynastic marriages played key roles in regional power, inheritance, and political alliances.
  • D. medieval German statesman
    A medieval German statesman is a political leader or advisor within the fragmented principalities and city-states of the Holy Roman Empire, responsible for governance, diplomacy, and the administration of law and territory.
  • E. German duke chosen
    A German duke is a high-ranking nobleman historically ruling or holding hereditary authority over a duchy within the German-speaking territories of the Holy Roman Empire and its successor states.
  • F. None of above.

Provenance (1 batch)

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_69f76db717088190811b4e744610f37d completed May 3, 2026, 3:45 p.m.
Created at: May 3, 2026, 3:59 p.m.