Triple
T19732097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John D. Rockefeller IV |
E473880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rockefeller family member |
C17393
|
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: Rockefeller family member Context triple: [John D. Rockefeller IV, instanceOf, Rockefeller family member]
-
A.
member of the Rockefeller family
chosen
A member of the Rockefeller family is an individual descended from or closely related to the historically influential American Rockefeller lineage, known for its vast wealth, philanthropy, and impact on industry and public life.
-
B.
member of the Astor family
A member of the Astor family is an individual belonging by birth or marriage to the historically prominent Astor lineage, known for its substantial wealth, social influence, and philanthropic legacy.
-
C.
member of the Rothschild family
A member of the Rothschild family is an individual belonging by birth or marriage to the historically influential European banking dynasty known for its significant roles in finance, philanthropy, and culture.
-
D.
member of the du Pont family
A member of the du Pont family is an individual belonging by birth or marriage to the historically prominent American industrial and philanthropic dynasty associated with the DuPont company.
-
E.
member of the Guggenheim family
A member of the Guggenheim family is an individual belonging by birth or marriage to the prominent American Guggenheim lineage known for its mining fortune, philanthropy, and patronage of modern art and culture.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:47 p.m.