Triple
T5571456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonanza Kings |
E146210
|
entity |
| Predicate | wealthUse |
P31294
|
FINISHED |
| Object | philanthropy by some members |
—
|
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: philanthropy by some members | Statement: [Bonanza Kings, wealthUse, philanthropy by some members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wealthUse Context triple: [Bonanza Kings, wealthUse, philanthropy by some members]
-
A.
incomeUsedFor
chosen
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
-
B.
economicUse
Indicates that one entity utilizes another for economic purposes, such as production, trade, revenue generation, or cost-saving activities.
-
C.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
D.
economicGoal
Indicates that an entity has a targeted economic outcome or objective it aims to achieve.
-
E.
economicStatus
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020502a288190af37f9ebb88fccae |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.