Triple
T13880487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huw Morgan |
E333700
|
entity |
| Predicate | centralEmotion |
P68365
|
FINISHED |
| Object | nostalgia for lost valley |
—
|
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: nostalgia for lost valley | Statement: [Huw Morgan, centralEmotion, nostalgia for lost valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralEmotion Context triple: [Huw Morgan, centralEmotion, nostalgia for lost valley]
-
A.
primaryEmotion
chosen
Indicates the main or most dominant emotion that an entity is experiencing or expressing in a given context.
-
B.
secondaryEmotion
Indicates that one emotion arises as a secondary, derivative, or reactive feeling in response to a primary emotion.
-
C.
emotionalCoreOf
Indicates that one entity serves as the central source, essence, or primary driver of another entity’s emotional character or experience.
-
D.
emotionState
Indicates the emotional condition or feeling that an entity is currently experiencing.
-
E.
emotionDomain
Indicates the general emotional category or type to which a specific emotion belongs (e.g., grouping emotions into broader domains like joy, anger, or fear).
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:15 p.m.