Triple
T20505132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deor |
E503407
|
entity |
| Predicate | consolatoryStrategy |
P54487
|
FINISHED |
| Object | exempla of past hardships that ended |
—
|
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: exempla of past hardships that ended | Statement: [Deor, consolatoryStrategy, exempla of past hardships that ended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolatoryStrategy Context triple: [Deor, consolatoryStrategy, exempla of past hardships that ended]
-
A.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
B.
copingMechanism
chosen
Indicates a way in which an entity responds to, manages, or adapts to stress, difficulty, or emotional challenges.
-
C.
relie
Indicates that one entity provides relief, comfort, or alleviation from distress, pain, or difficulty for another entity.
-
D.
relief
Indicates a state or action in which distress, pain, or difficulty is reduced, eased, or removed for an entity.
-
E.
oftenHelps
Indicates that one entity frequently provides assistance or support to another.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc66f00819083c804535e045545 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.