Triple
T18144362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thorne family |
E434345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gentry family |
C12475
|
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: gentry family Context triple: [The Thorne family, instanceOf, gentry family]
-
A.
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.
-
B.
Border Reiver family
A Border Reiver family is a kin-based group from the Anglo-Scottish borderlands (c. 13th–17th centuries) whose livelihood, identity, and power were rooted in raiding, cattle theft, and shifting allegiances rather than stable agrarian or feudal structures.
-
C.
Georgian family
A Georgian family is a close-knit household typically spanning multiple generations, characterized by strong traditions, deep respect for elders, and warm hospitality rooted in Georgian culture.
-
D.
patron family
A patron family is a socially or economically influential household that provides ongoing support, protection, or resources to individuals, groups, or institutions in exchange for loyalty, services, or prestige.
-
E.
landowning family
chosen
A landowning family is a kinship group whose social status, wealth, and influence are primarily derived from the ownership, control, and management of significant tracts of land across 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.