Triple
T26361892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince John of England and Scotland |
E660229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Stuart dynasty member |
C4891
|
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: Stuart dynasty member Context triple: [Prince John of England and Scotland, instanceOf, Stuart dynasty member]
-
A.
member of the House of Stuart
chosen
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.
-
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.
Stuart monarch
A Stuart monarch is a ruler from the Stuart dynasty who governed Scotland, England, and later Great Britain between the late 16th and early 18th centuries, overseeing significant political, religious, and constitutional change.
-
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 Stewart family
A member of the Stewart family is an individual who belongs by birth, marriage, or legal relation to the familial group identified by the Stewart surname and its shared lineage, traditions, and relationships.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:52 p.m.