Triple
T4891180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippa of Lancaster |
E109565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Lancaster member |
C16580
|
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 Lancaster member Context triple: [Philippa of Lancaster, instanceOf, House of Lancaster member]
-
A.
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.
-
B.
member of the Tudor dynasty
A member of the Tudor dynasty is an individual belonging by blood or lawful succession to the royal house that ruled England and Wales from 1485 to 1603, originating with Henry VII and ending with Elizabeth I.
-
C.
member of the House of Stuart
A member of the House of Stuart is an individual belonging by birth or legitimate descent to the royal dynasty that ruled Scotland and later England, Great Britain, and Ireland between the late 14th and early 18th centuries.
-
D.
House of Wessex member
A House of Wessex member is an individual belonging to the early medieval royal dynasty that ruled the Anglo-Saxon kingdom of Wessex and later much of England.
-
E.
House of Lancaster
The House of Lancaster was a cadet branch of the English royal House of Plantagenet that held the throne during parts of the 14th and 15th centuries and played a central role in the Wars of the Roses.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:28 p.m.