Triple
T37358262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dies Bildnis ist bezaubernd schön |
E927511
|
entity |
| Predicate | characterEmotion |
P75115
|
FINISHED |
| Object | rapturous love |
—
|
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: rapturous love | Statement: [Dies Bildnis ist bezaubernd schön, characterEmotion, rapturous love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterEmotion Context triple: [Dies Bildnis ist bezaubernd schön, characterEmotion, rapturous love]
-
A.
emotionChip
Indicates that an entity possesses or is equipped with an emotion chip that enables emotional processing or simulation.
-
B.
emotionDisplayed
chosen
Indicates that an entity is outwardly expressing or showing a particular emotion.
-
C.
emotionPersonified
Indicates that an abstract emotion is represented or depicted as if it were a person or human-like agent.
-
D.
faceExpression
Indicates the specific facial expression an entity is displaying, capturing its visible emotional or expressive state.
-
E.
intendedEmotion
Indicates the emotion that an action, expression, or communication is meant to evoke in its target, regardless of the actual emotion experienced.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:16 p.m.