Triple
T31670493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helena Richese |
E808256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of House Richese |
C61165
|
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: member of House Richese Context triple: [Helena Richese, instanceOf, member of House Richese]
-
A.
member of House Florent
A member of House Florent is an individual belonging to the noble Florent family of the Reach, defined by their lineage, heraldry, and social and political ties within Westerosi highborn society.
-
B.
member of the House of Ivrea
A member of the House of Ivrea is an individual belonging to the medieval European noble dynasty of Frankish origin that ruled or influenced several regions, including Italy and parts of France, through hereditary titles and political alliances.
-
C.
member of the House of Este
A member of the House of Este is an individual belonging to the historic Italian noble dynasty that ruled territories such as Ferrara, Modena, and Reggio and played a significant role in European politics and culture from the Middle Ages onward.
-
D.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
E.
member of the Savelli family
A member of the Savelli family is an individual belonging to the historically influential Roman noble lineage known for its political, ecclesiastical, and social prominence, particularly during the Middle Ages and Renaissance.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:01 p.m.