Triple
T22002872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugger family |
E543376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance banking house |
C24056
|
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: Renaissance banking house Context triple: [Fugger family, instanceOf, Renaissance banking house]
-
A.
Florentine banker
A Florentine banker is a financial professional from Renaissance Florence who manages deposits, loans, currency exchange, and investments for merchants, nobles, and governments within an emerging international banking network.
-
B.
Italian banker
An Italian banker is a financial professional from Italy who manages banking operations such as lending, investments, and client accounts within the Italian and international financial systems.
-
C.
merchant dynasty
chosen
A merchant dynasty is a powerful family or lineage whose wealth, influence, and social status are built and sustained over generations through large-scale trade and commercial enterprises.
-
D.
Florentine guild
A Florentine guild was a powerful medieval and Renaissance association of artisans, merchants, or professionals in Florence that regulated trade, protected members’ interests, and played a central role in the city’s economic and political 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:20 p.m.