Triple
T26314802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surviving Mommie Dearest |
E661938
|
entity |
| Predicate | workExpandedFrom |
P159797
|
FINISHED |
| Object | Mommie Dearest |
—
|
NE NERFINISHED |
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: Mommie Dearest | Statement: [Surviving Mommie Dearest, workExpandedFrom, Mommie Dearest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workExpandedFrom Context triple: [Surviving Mommie Dearest, workExpandedFrom, Mommie Dearest]
-
A.
workExpandedEdition
chosen
Indicates that one work is an expanded edition of another, containing additional or revised material beyond the original.
-
B.
expandsOnWork
Indicates that one work builds upon, elaborates, or extends the content, ideas, or results of another work.
-
C.
wasExpandedIn
Indicates that something increased in size, scope, or extent during a specified time or event.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 10:24 p.m.