Triple
T1906016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pap Finn |
E38005
|
entity |
| Predicate | deathStatusInNovel |
P24966
|
FINISHED |
| Object | dies offstage |
—
|
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: dies offstage | Statement: [Pap Finn, deathStatusInNovel, dies offstage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathStatusInNovel Context triple: [Pap Finn, deathStatusInNovel, dies offstage]
-
A.
deathStatus
chosen
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
B.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
C.
deathDescribedAs
Indicates that one entity characterizes, portrays, or refers to another entity’s death using a particular description, metaphor, or wording.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
deathBefore
Indicates that one entity’s death occurred earlier in time than another entity’s death.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.