Triple
T33982831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trivulzio family |
E871330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Milanese noble family |
C21254
|
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: Milanese noble family Context triple: [Trivulzio family, instanceOf, Milanese noble family]
-
A.
Milanese patrician family
chosen
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.
Genoese patrician family
A Genoese patrician family is a noble lineage from the Republic of Genoa that held hereditary political power, economic influence, and social prestige within the city’s oligarchic ruling class.
-
D.
Sicilian noble family
A Sicilian noble family is an aristocratic lineage rooted in Sicily, historically distinguished by hereditary titles, landownership, and influence over regional politics, culture, and social life.
-
E.
Venetian family
A Venetian family is a social unit rooted in Venice’s unique historical, cultural, and economic context, typically characterized by strong kinship ties, intergenerational traditions, and connections to the city’s maritime, mercantile, or artistic heritage.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.