Triple

T17668755
Position Surface form Disambiguated ID Type / Status
Subject Eustace II, Count of Boulogne E440457 entity
Predicate instanceOf P0 FINISHED
Object participant in the Norman Conquest of England C33211 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: participant in the Norman Conquest of England
Context triple: [Eustace II, Count of Boulogne, instanceOf, participant in the Norman Conquest of England]
  • A. event in the Norman Conquest of England
    An event in the Norman Conquest of England is a specific historical occurrence between 1066 and 1071 that contributed to William of Normandy’s seizure and consolidation of power over England.
  • B. Norman ruler
    A Norman ruler is a sovereign or feudal lord of Norman origin who exercises political and military authority over a territory, often characterized by a blend of Viking heritage and Frankish culture.
  • C. participant in the Hundred Years' War
    A participant in the Hundred Years' War is any individual, military unit, political leader, or supporting actor directly involved in the political, diplomatic, or military activities of the intermittent conflicts between England, France, and their allies from 1337 to 1453.
  • D. member of the Norman nobility chosen
    A member of the Norman nobility is an individual belonging to the hereditary warrior-aristocratic elite of Norman society, holding land, titles, and political influence derived from feudal bonds and conquest.
  • E. Anglo-Saxon ruler
    An Anglo-Saxon ruler is a monarch or chieftain who governed territories in early medieval England, exercising military, legal, and religious authority over their people.
  • 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
Created at: April 10, 2026, 9:58 a.m.