Triple
T13482527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokujo no Miyasudokoro |
E318405
|
entity |
| Predicate | deathCauseInText |
P44824
|
FINISHED |
| Object | implied to be related to emotional and spiritual turmoil |
—
|
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: implied to be related to emotional and spiritual turmoil | Statement: [Rokujo no Miyasudokoro, deathCauseInText, implied to be related to emotional and spiritual turmoil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathCauseInText Context triple: [Rokujo no Miyasudokoro, deathCauseInText, implied to be related to emotional and spiritual turmoil]
-
A.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
reasonForDeath
chosen
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
D.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
E.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3868ec8190a6a1803018d4f2d8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.