Triple
T6224401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florence Adele Vanderbilt Twombly |
E139193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vanderbilt family member |
C6654
|
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: Vanderbilt family member Context triple: [Florence Adele Vanderbilt Twombly, instanceOf, Vanderbilt family member]
-
A.
member of the Vanderbilt family
chosen
A member of the Vanderbilt family is an individual descended from or legally adopted into the historically prominent American Vanderbilt lineage, known for its 19th-century railroad and shipping fortune and enduring social influence.
-
B.
member of the Rockefeller family
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.
-
C.
member of the Rogers family
A member of the Rogers family is an individual who belongs to the Rogers household by blood, marriage, or adoption and participates in its shared relationships, responsibilities, and traditions.
-
D.
member of the Ford family
A member of the Ford family is an individual who belongs by birth, marriage, or legal adoption to the familial lineage associated with the Ford surname and its shared history, relationships, and traditions.
-
E.
member of the Roebling family
A member of the Roebling family is an individual belonging to the historically significant American engineering and industrial dynasty best known for designing and constructing the Brooklyn Bridge.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:22 p.m.