Triple
T13476475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond VII, Count of Toulouse |
E318264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Narbonne |
C33079
|
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: Duke of Narbonne Context triple: [Raymond VII, Count of Toulouse, instanceOf, Duke of Narbonne]
-
A.
Duke of Vendôme
The Duke of Vendôme is a noble title historically associated with the French peerage, often held by prominent members of the Bourbon-Vendôme branch of the royal family.
-
B.
Duke of Brittany
The Duke of Brittany was the sovereign or semi-sovereign ruler of the historical Duchy of Brittany in western France, holding feudal authority, managing regional governance, and often navigating complex political relations with the French crown and neighboring powers.
-
C.
Duke of Savoy
The Duke of Savoy was the hereditary ruler of the historical Duchy of Savoy, a significant European principality that played a key role in the politics of Italy and France from the late Middle Ages until its elevation to a kingdom.
-
D.
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.
-
E.
Duke of Lorraine
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:42 p.m.