Triple
T34196062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emelecistas |
E877243
|
entity |
| Predicate | collectiveEmotion |
P76175
|
FINISHED |
| Object | high enthusiasm |
—
|
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: high enthusiasm | Statement: [Emelecistas, collectiveEmotion, high enthusiasm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveEmotion Context triple: [Emelecistas, collectiveEmotion, high enthusiasm]
-
A.
emotionSpectrumAffiliation
Indicates an entity’s association or alignment with a particular range or category of emotions along an emotional spectrum.
-
B.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
C.
emotionState
chosen
Indicates the emotional condition or feeling that an entity is currently experiencing.
-
D.
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).
-
E.
provokesEmotionType
Indicates that one entity causes or elicits a specific type of emotional response in another entity.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:55 a.m.