Triple
T27318690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yolanda of Courtenay |
E689422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Courtenay member |
C22588
|
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: House of Courtenay member Context triple: [Yolanda of Courtenay, instanceOf, House of Courtenay member]
-
A.
member of the House of Courtenay
chosen
A member of the House of Courtenay is an individual belonging by birth or legitimate descent to the medieval noble family of Courtenay, historically influential in France and England through feudal lordships, crusading activity, and dynastic alliances.
-
B.
member of the de Burgh family
A member of the de Burgh family is an individual belonging to the historically significant Anglo-Norman noble lineage known for its political influence and landholdings in medieval Ireland and England.
-
C.
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.
-
D.
House of Lancaster member
A House of Lancaster member is an individual belonging to the English royal dynasty that held the throne during parts of the late Middle Ages, notably in the Wars of the Roses.
-
E.
member of the House of Plantagenet
A member of the House of Plantagenet is an individual belonging to the medieval royal dynasty that ruled England and parts of France from the mid-12th to the late 15th century, known for its influential monarchs, dynastic conflicts, and role in shaping English law and governance.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:32 a.m.