Triple
T35785305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassoon family |
E1034548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mercantile family |
C64361
|
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: mercantile family Context triple: [Sassoon family, instanceOf, mercantile family]
-
A.
member of merchant family
A member of a merchant family is an individual born or integrated into a household whose primary livelihood and social identity are rooted in trade, commerce, and the management of goods or financial transactions.
-
B.
shipowning family
A shipowning family is a lineage-based group that collectively owns, manages, and derives income from one or more commercial vessels, often integrating maritime business decisions with family governance and succession.
-
C.
19th-century business family
A 19th-century business family is a kinship-based household whose members collectively own, manage, and pass down commercial enterprises, blending domestic life with entrepreneurial activity and social status in the context of industrializing economies.
-
D.
noble family
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
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. 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.