Triple
T25112392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Vanderbilt |
E629030
|
entity |
| Predicate | notableFamilyWealthSource |
P9503
|
FINISHED |
| Object | railroads |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: railroads | Statement: [Grace Vanderbilt, notableFamilyWealthSource, railroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyWealthSource Context triple: [Grace Vanderbilt, notableFamilyWealthSource, railroads]
-
A.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
B.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
C.
notableHolderFamily
Indicates that a particular family is notably associated with holding, possessing, or being custodians of the referenced entity.
-
D.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
E.
hasWealthSource
chosen
Indicates that an entity derives its wealth or financial resources from a specified source.
- F. None of above.
Provenance (3 batches)
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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 18, 2026, 6:27 a.m.