Triple
T20678218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraxas Malfoy |
E508216
|
entity |
| Predicate | familyWealthStatus |
P2987
|
FINISHED |
| Object | wealthy |
—
|
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: wealthy | Statement: [Abraxas Malfoy, familyWealthStatus, wealthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyWealthStatus Context triple: [Abraxas Malfoy, familyWealthStatus, wealthy]
-
A.
isWealthy
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
B.
wealthDescribedAs
Indicates that one entity’s wealth is characterized, portrayed, or expressed in terms of another entity or description.
-
C.
economicStatus
chosen
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
-
D.
spouseWealthStatus
Indicates the financial status or wealth level of a person’s spouse in relation to that person.
-
E.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea354f0819094e9ee8d3adaa221 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.