Triple
T24567447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cencio Savelli |
E607831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Savelli family |
C48461
|
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 Savelli family Context triple: [Cencio Savelli, instanceOf, member of the Savelli family]
-
A.
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.
-
B.
member of the Barberini family
A member of the Barberini family is an individual belonging to the influential Italian noble lineage that rose to prominence in the 17th century, notably through Pope Urban VIII and their extensive political, cultural, and artistic patronage.
-
C.
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.
-
D.
member of the Borghese family
A member of the Borghese family is an individual belonging to the historically influential Italian noble house known for its political power, patronage of the arts, and close ties to the Catholic Church.
-
E.
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.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:28 a.m.