Triple
T3057211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iasion |
E60509
|
entity |
| Predicate | reasonForDeath |
P44824
|
FINISHED |
| Object | love affair with Demeter |
—
|
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: love affair with Demeter | Statement: [Iasion, reasonForDeath, love affair with Demeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDeath Context triple: [Iasion, reasonForDeath, love affair with Demeter]
-
A.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
D.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
E.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
- F. None of above. chosen
Provenance (4 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e162d148190969fb422a45d052c |
completed | March 8, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.