Triple
T23684330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schøller family of Trondheim merchants |
E585121
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian merchant family |
C45685
|
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: Norwegian merchant family Context triple: [Schøller family of Trondheim merchants, instanceOf, Norwegian merchant family]
-
A.
Dutch patrician family
A Dutch patrician family is a historically prominent, often urban-based lineage belonging to the higher bourgeois elite of the Netherlands, distinguished by long-standing social status, wealth, and influence in commerce, politics, or culture.
-
B.
Norwegian family
chosen
A Norwegian family is a social unit typically consisting of parents and children in Norway, characterized by strong welfare support, egalitarian values, and a balance between close-knit bonds and individual independence.
-
C.
Swedish noble family
A Swedish noble family is a lineage of individuals in Sweden historically granted hereditary noble status, often holding titles, estates, and social privileges recognized by the Swedish nobility system.
-
D.
Danish family
A Danish family is a close-knit household unit in Denmark characterized by egalitarian values, strong social support systems, and a balanced emphasis on work-life harmony.
-
E.
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.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:52 p.m.