Triple
T19822866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noccalula |
E476241
|
entity |
| Predicate | deathMannerInLegend |
P100625
|
FINISHED |
| Object | suicide by jumping from a waterfall |
—
|
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: suicide by jumping from a waterfall | Statement: [Noccalula, deathMannerInLegend, suicide by jumping from a waterfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathMannerInLegend Context triple: [Noccalula, deathMannerInLegend, suicide by jumping from a waterfall]
-
A.
legendaryDeath
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
B.
deathTypeInFiction
Indicates the manner or category of how a character dies within a fictional narrative.
-
C.
deifiedPersonDeathCause
Indicates the cause or manner of death of the person who is venerated or treated as a deity.
-
D.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
E.
legendaryCauseOfDeath
chosen
Indicates a legendary or mythic account of how an entity died, as opposed to a historically verified cause of 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654ffb37c8190be540a793befe16c |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.