Triple
T20336249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sparkman family of Tampa |
E492618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prominent local family |
C9457
|
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: prominent local family Context triple: [Sparkman family of Tampa, instanceOf, prominent local family]
-
A.
prominent family
chosen
A prominent family is a socially influential and widely recognized household whose members hold significant power, status, or visibility within a community or society.
-
B.
local family
A local family is a group of related individuals who live within the same community or geographic area, sharing daily life, resources, and social ties rooted in that locality.
-
C.
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.
-
D.
philanthropic family
A philanthropic family is a household whose members intentionally dedicate their collective resources, time, and influence to charitable causes and community betterment across generations.
-
E.
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.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:23 a.m.