Triple
T333522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Tsai |
E6674
|
entity |
| Predicate | netWorth |
P199
|
FINISHED |
| Object | multi-billionaire |
—
|
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: multi-billionaire | Statement: [Joe Tsai, netWorth, multi-billionaire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: netWorth Context triple: [Joe Tsai, netWorth, multi-billionaire]
-
A.
netWorthStatus
chosen
Indicates the financial standing or wealth level of an entity relative to defined net worth categories or thresholds.
-
B.
netWorthAtDeath
Indicates the total value of a person’s assets minus liabilities at the time of their death.
-
C.
netIncome
Indicates the financial result of an entity’s operations over a period, calculated as total revenues minus all expenses, taxes, and other deductions.
-
D.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
E.
hasWealthSource
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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac4d9d081908a624464e450fb0e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.