Triple
T19020612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aesacus |
E465473
|
entity |
| Predicate | griefOver |
P44213
|
FINISHED |
| Object | death of Hesperia |
—
|
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: death of Hesperia | Statement: [Aesacus, griefOver, death of Hesperia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: griefOver Context triple: [Aesacus, griefOver, death of Hesperia]
-
A.
grievesFor
chosen
Indicates that one entity feels grief or sorrow because of the loss, suffering, or misfortune of another entity.
-
B.
mourningLevel
Indicates the degree or intensity to which an entity is experiencing or expressing mourning in response to a loss.
-
C.
mourningIntensifiesIn
Indicates that the level or expression of mourning becomes stronger or more intense within a specified context, period, or situation.
-
D.
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.
-
E.
mourningPeriodBegins
Indicates that the formal period of mourning for a death or loss has started.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6de93408190a98dea2319f1af62 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.