Triple
T4732196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yolande of Dreux |
E105035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 13th-century French noble |
C2373
|
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: 13th-century French noble Context triple: [Yolande of Dreux, instanceOf, 13th-century French noble]
-
A.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
B.
French nobleman
A French nobleman is an aristocratic male from France who holds hereditary or granted titles, privileges, and social status within the traditional hierarchical nobility system.
-
C.
13th-century English noblewoman
A 13th-century English noblewoman is an aristocratic woman of medieval England who managed estates, forged political and marital alliances, and navigated the social, legal, and religious constraints of feudal society.
-
D.
French noblewoman
chosen
A French noblewoman is an aristocratic woman from France who holds or inherits a noble title, typically associated with high social status, land ownership, and influence within the historical French social hierarchy.
-
E.
14th-century English noblewoman
A 14th-century English noblewoman is an aristocratic woman of medieval England who holds social status and influence through birth or marriage, managing estates, patronage, and family alliances within a feudal and patriarchal society.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:19 p.m.