Triple
T12712584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Q |
E303756
|
entity |
| Predicate | associatedWithWealthStatus |
P95466
|
FINISHED |
| Object | very rich |
—
|
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: very rich | Statement: [Old Q, associatedWithWealthStatus, very rich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWealthStatus Context triple: [Old Q, associatedWithWealthStatus, very rich]
-
A.
isWealthy
chosen
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
B.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
C.
wealthDescribedAs
Indicates that one entity’s wealth is characterized, portrayed, or expressed in terms of another entity or description.
-
D.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
E.
spouseWealthStatus
Indicates the financial status or wealth level of a person’s spouse in relation to that person.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96208fa6481909d6fd43654752a2d |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.