Triple
T21186514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garisenda family |
E522093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Italian noble family |
C26458
|
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: medieval Italian noble family Context triple: [Garisenda family, instanceOf, medieval Italian noble family]
-
A.
Milanese patrician family
A Milanese patrician family is a historically prominent, aristocratic lineage from Milan that held social, political, and economic influence within the city’s elite ruling class.
-
B.
Florentine patrician family
A Florentine patrician family is a prominent, aristocratic lineage in Renaissance Florence whose wealth, political influence, and social status shaped the city’s governance, culture, and economic life.
-
C.
medieval Roman noble family
A medieval Roman noble family is an aristocratic lineage based in Rome during the Middle Ages, wielding political, economic, and social influence through landholdings, alliances, and roles in civic and ecclesiastical institutions.
-
D.
Occitan noble family
An Occitan noble family is a lineage of aristocratic households originating from the historical Occitania region in southern Europe, distinguished by hereditary titles, landholdings, and regional cultural influence.
-
E.
Italian dynasty
chosen
An Italian dynasty is a hereditary ruling family originating from Italy that maintains political, social, or economic power across multiple generations.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.