Triple
T22350726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonso d’Aragona |
E552519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Aragonese dynasty of Naples |
C46147
|
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 the Aragonese dynasty of Naples Context triple: [Alfonso d’Aragona, instanceOf, member of the Aragonese dynasty of Naples]
-
A.
Ascanian dynasty member
An Ascanian dynasty member is an individual belonging to the medieval and early modern German noble house of Ascania, which ruled various principalities such as Anhalt, Brandenburg, and Saxony.
-
B.
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.
-
C.
Italian dynasty
An Italian dynasty is a hereditary ruling family originating from Italy that maintains political, social, or economic power across multiple generations.
-
D.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
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. 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.