Triple
T31656211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amy Wong |
E807863
|
entity |
| Predicate | parentsWealthSource |
P9503
|
FINISHED |
| Object | Mars real estate |
—
|
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: Mars real estate | Statement: [Amy Wong, parentsWealthSource, Mars real estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentsWealthSource Context triple: [Amy Wong, parentsWealthSource, Mars real estate]
-
A.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
B.
hasWealthSource
chosen
Indicates that an entity derives its wealth or financial resources from a specified source.
-
C.
parentsAffiliation
Indicates that the parents are associated with, belong to, or are formally connected to a particular organization, group, or institution.
-
D.
managesWealthFor
Indicates that one entity is responsible for overseeing, controlling, or administering the financial assets or wealth of another entity.
-
E.
usesWealthFor
Indicates that one entity directs or allocates its wealth or financial resources toward another entity or purpose.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 30, 2026, 10:55 p.m.