Triple

T27160666
Position Surface form Disambiguated ID Type / Status
Subject Rohese de Vere E682650 entity
Predicate instanceOf P0 FINISHED
Object Anglo-Norman aristocrat 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: Anglo-Norman aristocrat
Context triple: [Rohese de Vere, instanceOf, Anglo-Norman aristocrat]
  • A. Anglo-French nobleman
    An Anglo-French nobleman is an aristocrat whose lineage, titles, or holdings span both English and French realms, embodying the intertwined political, cultural, and familial ties between the two nobilities.
  • B. Anglo-Breton noble
    An Anglo-Breton noble is a medieval aristocrat of mixed English and Breton heritage who held land, titles, and political influence across both regions, often serving as a cultural and military intermediary between them.
  • C. 14th-century English noble
    A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
  • 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. French nobleman
    A French nobleman is an aristocratic male from France who holds hereditary or granted titles, privileges, and social status within the traditional hierarchical nobility system.
  • 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_69eefacf6e788190a75a64399d9e3109 completed April 27, 2026, 5:57 a.m.
Created at: April 27, 2026, 9:18 a.m.