Triple
T23753639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfons de Borja |
E587043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Borgia family member |
C22813
|
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: Borgia family member Context triple: [Alfons de Borja, instanceOf, Borgia family member]
-
A.
member of the Borgia family
chosen
A member of the Borgia family is an individual belonging to the influential Italian-Spanish noble lineage renowned for its significant political, religious, and cultural impact during the Renaissance, often associated with power, intrigue, and controversy.
-
B.
member of the Pazzi family
A member of the Pazzi family is an individual belonging by birth or marriage to the historically influential Florentine noble house known for its political ambitions, banking activities, and role in the Pazzi Conspiracy against the Medici.
-
C.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
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 Visconti dynasty
A member of the Visconti dynasty is an individual belonging to the powerful medieval and Renaissance noble family that ruled Milan and surrounding territories in northern Italy.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:13 p.m.