Triple
T8563469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Ivanovich |
E202743
|
entity |
| Predicate | thinksAboutAtFuneral |
P83663
|
FINISHED |
| Object | his own promotion |
—
|
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: his own promotion | Statement: [Peter Ivanovich, thinksAboutAtFuneral, his own promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thinksAboutAtFuneral Context triple: [Peter Ivanovich, thinksAboutAtFuneral, his own promotion]
-
A.
mourningCause
Indicates that one entity is in a state of mourning specifically because of the other entity, which is the cause or reason for the grief.
-
B.
mourningCustom
Indicates a culturally prescribed way in which people are expected to express grief and honor the dead after a loss.
-
C.
associatedAfterlife
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
D.
mourningMotif
Indicates a recurring theme or pattern in which grief, lamentation, or sorrow over loss is expressed or symbolically represented.
-
E.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9cfc4a48190ae4530d3614d115f |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.