Triple
T29818870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Benedict Stuart |
E757188
|
entity |
| Predicate | lastLegitimateMaleLineDescendantOf |
P98182
|
FINISHED |
| Object | House of Stuart |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: House of Stuart | Statement: [Henry Benedict Stuart, lastLegitimateMaleLineDescendantOf, House of Stuart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastLegitimateMaleLineDescendantOf Context triple: [Henry Benedict Stuart, lastLegitimateMaleLineDescendantOf, House of Stuart]
-
A.
lastLegitimateMaleHeirOf
chosen
Indicates that one entity is the final male descendant in a legitimate line of succession or inheritance from another entity.
-
B.
heirThroughFemaleLine
Indicates that one entity is the heir of another specifically through a lineage traced via female ancestors.
-
C.
hasNotableMaleBearer
Indicates that an entity has at least one well-known or prominent male individual associated with bearing its name or title.
-
D.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
E.
paternalLineageTitle
Indicates the title or designation an entity holds specifically through its paternal line of descent.
- F. None of above.
Provenance (3 batches)
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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6756578ec8190b4fe425dfc08c50a |
completed | May 2, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:28 p.m.