Triple
T2466671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John A. Roebling II |
E55266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Roebling family |
C11002
|
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: member of the Roebling family Context triple: [John A. Roebling II, instanceOf, member of the Roebling family]
-
A.
member of the Packard family
A member of the Packard family is an individual who belongs by birth, marriage, or legal relation to the lineage or household identified by the Packard surname.
-
B.
member of the Vanderbilt family
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.
-
C.
member of the Stanley family
A member of the Stanley family is an individual who belongs by birth, marriage, or adoption to the familial group identified by the shared Stanley surname and its associated relationships, traditions, and lineage.
-
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 Trump family
A member of the Trump family is an individual related by blood, marriage, or adoption to the lineage of the American Trump household, notably associated with businessman and former U.S. President Donald J. Trump.
- F. None of above. chosen
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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:44 p.m.