Triple
T10418741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles |
E245587
|
entity |
| Predicate | deathStatusInWork |
P51466
|
FINISHED |
| Object | dies at the end of the novella |
—
|
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 at the end of the novella | Statement: [Miles, deathStatusInWork, dies at the end of the novella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathStatusInWork Context triple: [Miles, deathStatusInWork, dies at the end of the novella]
-
A.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
B.
deathOutcome
chosen
Indicates that an event, condition, or action results in the death of the affected entity.
-
C.
deathConsidered
Indicates that one entity regards or evaluates another entity’s death (or the prospect of it) in some way, such as judging its acceptability, significance, or implications.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
deathIs
Indicates that one entity is the cause, manner, or circumstance of 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2938188190a908316d0a0959be |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:11 p.m.