Triple
T23896465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheryl Blossom |
E600914
|
entity |
| Predicate | hasFamilyWealthSource |
P9503
|
FINISHED |
| Object | Blossom family business |
—
|
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: Blossom family business | Statement: [Cheryl Blossom, hasFamilyWealthSource, Blossom family business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyWealthSource Context triple: [Cheryl Blossom, hasFamilyWealthSource, Blossom family business]
-
A.
hasWealthSource
chosen
Indicates that an entity derives its wealth or financial resources from a specified source.
-
B.
hasPrivateWealth
Indicates that an entity possesses personal financial assets or wealth that are privately owned and not part of shared or public resources.
-
C.
hasTrustFund
Indicates that an entity possesses or benefits from a trust fund established to hold and manage assets for them.
-
D.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
E.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdda39448190bdefa953e0558583 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.