Triple
T25770919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles II of Anjou |
E649017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | count of Provence |
C15583
|
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 Provence Context triple: [Charles II of Anjou, instanceOf, count of Provence]
-
A.
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.
-
B.
Count of Provence
chosen
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 Clermont-en-Beauvaisis
The Count of Clermont-en-Beauvaisis was a medieval French noble title associated with the lordship and county centered on the town of Clermont in the Beauvaisis region of northern France.
-
D.
Count of La Marche
The Count of La Marche is a noble title historically associated with the ruler of the La Marche region in central France, often held by influential medieval aristocratic families.
-
E.
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.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:29 a.m.