Triple
T24987723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoebe Forrester |
E625358
|
entity |
| Predicate | deathTypeInStory |
P90208
|
FINISHED |
| Object | tragic death |
—
|
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: tragic death | Statement: [Phoebe Forrester, deathTypeInStory, tragic death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathTypeInStory Context triple: [Phoebe Forrester, deathTypeInStory, tragic death]
-
A.
deathTypeInFiction
chosen
Indicates the manner or category of how a character dies within a fictional narrative.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
D.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
E.
deathLeadsTo
Indicates that one entity’s death causes, results in, or brings about another event, state, or condition.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490b14848190918c7a0e1f6abf3e |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:03 a.m.