Triple
T9527765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown family (local landowners) |
E229804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local notable 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: local notable family Context triple: [Brown family (local landowners), instanceOf, local notable 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.
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.
-
C.
family member of a notable person
A family member of a notable person is an individual related by blood, marriage, or adoption to someone widely recognized for their achievements, status, or public influence.
-
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.
political family
A political family is a group of related individuals who, across generations, hold or seek public office and wield political influence, often leveraging shared name recognition, networks, and resources.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8 p.m.