Triple
T22148108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen |
E547342
|
entity |
| Predicate | nameBearerWealthSource |
P147170
|
FINISHED |
| Object | Standard Oil heir |
—
|
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: Standard Oil heir | Statement: [Stephen, nameBearerWealthSource, Standard Oil heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearerWealthSource Context triple: [Stephen, nameBearerWealthSource, Standard Oil heir]
-
A.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
B.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
C.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
D.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
E.
wealthSymbol
Indicates that one entity serves as a representation or sign of wealth for another entity.
- F. None of above. chosen
Provenance (4 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f209688190afea1f275c922c73 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:33 p.m.