Triple
T16163068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert L. Johnson |
E392224
|
entity |
| Predicate | hasNetWorthCharacteristic |
P199
|
FINISHED |
| Object | billionaire status |
—
|
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: billionaire status | Statement: [Robert L. Johnson, hasNetWorthCharacteristic, billionaire status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetWorthCharacteristic Context triple: [Robert L. Johnson, hasNetWorthCharacteristic, billionaire status]
-
A.
netWorthStatus
chosen
Indicates the financial standing or wealth level of an entity relative to defined net worth categories or thresholds.
-
B.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
C.
isWealthy
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
D.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
E.
hasEconomicResource
Indicates that an entity possesses, controls, or has access to an economic resource (such as money, assets, or productive means) that can be used for economic activities or value creation.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e616770819093f16c88722b2a7d |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.