Triple
T37189591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nominoe |
E921413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | duke of Brittany |
C19330
|
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 Brittany Context triple: [Nominoe, instanceOf, duke of Brittany]
-
A.
Duke of Brittany
chosen
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.
-
B.
Duke of Aquitaine
The Duke of Aquitaine was a high-ranking noble title in medieval and early modern France, denoting the ruler of the historically significant and often semi-autonomous region of Aquitaine in southwestern France.
-
C.
Duke of Normandy
The Duke of Normandy was a medieval noble title denoting the sovereign or semi-sovereign ruler of the Duchy of Normandy, a powerful feudal territory in northwestern France that played a pivotal role in European politics, especially after its dukes became kings of England.
-
D.
Duke of Penthièvre
The Duke of Penthièvre is a French noble title historically associated with a high-ranking peer of France, often linked to the House of Bourbon and significant territorial and political influence in Brittany.
-
E.
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.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.