Triple
T1739271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Dream Within a Dream |
E37993
|
entity |
| Predicate | hasEmotionalCore |
P7863
|
FINISHED |
| Object | anguish over impermanence |
—
|
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: anguish over impermanence | Statement: [A Dream Within a Dream, hasEmotionalCore, anguish over impermanence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionalCore Context triple: [A Dream Within a Dream, hasEmotionalCore, anguish over impermanence]
-
A.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
B.
hasMood
chosen
Indicates that an entity is experiencing or characterized by a particular emotional or affective state.
-
C.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
D.
emotionallyAttachedTo
Indicates that one entity has a strong emotional bond, affection, or dependence directed toward another entity.
-
E.
hasCoreMember
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.