Triple
T32098518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonardo I Tocco |
E819782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Tocco family |
C61340
|
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 Tocco family Context triple: [Leonardo I Tocco, instanceOf, member of the Tocco family]
-
A.
member of the Gattilusio family
A member of the Gattilusio family is an individual belonging to the medieval Genoese noble lineage that ruled several Aegean islands and coastal territories under Byzantine and later Ottoman influence.
-
B.
member of the Conti di Segni family
A member of the Conti di Segni family is an individual belonging to the medieval Italian noble lineage from Segni, noted for producing influential churchmen, including several popes and cardinals.
-
C.
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.
-
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 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.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:26 a.m.