Triple

T15675977
Position Surface form Disambiguated ID Type / Status
Subject Alphonse, Count of Poitiers E377445 entity
Predicate instanceOf P0 FINISHED
Object Count of Poitiers C35706 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 Poitiers
Context triple: [Alphonse, Count of Poitiers, instanceOf, Count of Poitiers]
  • 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 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.
  • D. Count of Artois
    The Count of Artois was a medieval noble title designating the feudal ruler of the County of Artois in northern France, often held by influential members of the French royal family.
  • E. Count of Alençon
    The Count of Alençon is a noble title historically associated with the ruler of the County of Alençon in northwestern France, often held by members of the French royal or ducal families.
  • 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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
Created at: April 10, 2026, 4:16 a.m.