Triple

T8967864
Position Surface form Disambiguated ID Type / Status
Subject Robert, Count of Clermont E214183 entity
Predicate instanceOf P0 FINISHED
Object Count of Clermont-en-Beauvaisis C25381 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: Count of Clermont-en-Beauvaisis
Context triple: [Robert, Count of Clermont, instanceOf, Count of Clermont-en-Beauvaisis]
  • A. Count of Soissons
    The Count of Soissons was a medieval noble title associated with the governance and control of the County of Soissons in northern France, often held by influential aristocratic families involved in regional and royal politics.
  • B. Count of Toulouse
    The Count of Toulouse was a powerful medieval noble title in southern France, ruling the County of Toulouse and often wielding significant political, military, and cultural influence in the region and beyond.
  • C. Count of Vermandois
    The Count of Vermandois was a medieval noble title in northern France, held by various influential families who governed the county of Vermandois and played significant roles in Frankish and Capetian politics.
  • D. Count of Boulogne
    The Count of Boulogne was a medieval noble title associated with the County of Boulogne in northern France, held by various influential lords who controlled this strategically important coastal region.
  • E. Count of Provence
    The Count of Provence is a noble title historically held by the ruler of the County of Provence, a medieval feudal territory in what is now southeastern France, signifying both regional governance and aristocratic status.
  • F. None of above. chosen

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_69ca839dbf608190a2f5990477115d29 completed March 30, 2026, 2:07 p.m.
Created at: March 30, 2026, 7:01 p.m.