Triple
T11026771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter, Count of Alençon |
E260644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Count of Alençon |
C29033
|
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 Alençon Context triple: [Peter, Count of Alençon, instanceOf, Count of Alençon]
-
A.
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.
-
B.
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.
-
C.
Count of Anjou
The Count of Anjou was a medieval noble title in western France whose holders controlled the strategically important county of Anjou and often played a pivotal role in French and English royal politics.
-
D.
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.
-
E.
Count of Ponthieu
The Count of Ponthieu was a medieval noble title denoting the ruler of the coastal county of Ponthieu in northern France, strategically important for controlling access between Normandy and Flanders.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.