Triple
T17874326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selyse Baratheon |
E446911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of House Florent |
C39242
|
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 Florent Context triple: [Selyse Baratheon, instanceOf, member of House Florent]
-
A.
Florentine citizen
A Florentine citizen is an inhabitant of Florence, historically shaped by the city’s rich political, artistic, and commercial traditions and participating in its civic, cultural, and social life.
-
B.
Member of the House of Medici
A Member of the House of Medici is an individual belonging to the powerful Florentine banking and political dynasty that significantly influenced Renaissance art, culture, and European politics.
-
C.
Member of the House of Medici
A Member of the House of Medici is an individual belonging to the powerful Florentine banking and political dynasty that significantly influenced European finance, art, and politics from the 15th to 18th centuries.
-
D.
member of the Farnese family
A member of the Farnese family is an individual belonging to the influential Italian noble dynasty that rose to prominence in the Renaissance through political power, military leadership, and significant patronage of the arts and architecture.
-
E.
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.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:18 a.m.