Triple
T15132638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Del Griffith |
E361456
|
entity |
| Predicate | revealsBackstory |
P115645
|
FINISHED |
| Object | widower |
—
|
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: widower | Statement: [Del Griffith, revealsBackstory, widower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealsBackstory Context triple: [Del Griffith, revealsBackstory, widower]
-
A.
expandsBackstoryOf
chosen
Indicates that one entity provides additional background details or context that elaborate on the history or origins of another entity.
-
B.
hasFictionalBackstory
Indicates that an entity is associated with an invented or imaginary narrative background rather than a real-world history.
-
C.
protagonistBackground
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
-
D.
inUniverseBackstory
Indicates that one entity provides narrative background or history for another within the fictional universe itself, as opposed to external or meta commentary.
-
E.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b29a4c819087f8818e3f5788f5 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.