Triple
T35964827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard of Brittany |
E1040111
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Montfort |
C65459
|
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: member of the House of Montfort Context triple: [Richard of Brittany, instanceOf, member of the House of Montfort]
-
A.
member of the House of Montferrat
A member of the House of Montferrat is an individual belonging to the medieval Italian noble dynasty that ruled the Marquisate of Montferrat and held significant political and dynastic influence across Europe and the Crusader states.
-
B.
member of the Mortimer family
A member of the Mortimer family is an individual belonging by birth, marriage, or adoption to the Mortimer lineage, sharing its name, history, and familial relationships.
-
C.
member of the House of Dreux
A member of the House of Dreux is an individual belonging to the medieval French noble dynasty that originated as a cadet branch of the Capetian kings and held the county of Dreux and other significant feudal titles.
-
D.
member of the House of Lusignan
A member of the House of Lusignan is an individual belonging to the medieval French noble dynasty that rose to prominence as lords of Lusignan and later as kings of Jerusalem, Cyprus, and Armenia.
-
E.
member of the House of Albret
A member of the House of Albret is an individual belonging to the historic French noble family that held significant feudal, political, and dynastic influence, particularly in southwestern France and Navarre, from the Middle Ages into the early modern period.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.