Triple
T8885388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaf Coneybear |
E211515
|
entity |
| Predicate | emotionalFunction |
P52747
|
FINISHED |
| Object | evokes sympathy from the audience |
—
|
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: evokes sympathy from the audience | Statement: [Leaf Coneybear, emotionalFunction, evokes sympathy from the audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalFunction Context triple: [Leaf Coneybear, emotionalFunction, evokes sympathy from the audience]
-
A.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
B.
emotionEffect
chosen
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
C.
emotionState
Indicates the emotional condition or feeling that an entity is currently experiencing.
-
D.
emotionAssociation
Indicates an emotional relationship or connection that one entity has toward another entity or concept.
-
E.
emotionDisplayed
Indicates that an entity is outwardly expressing or showing a particular emotion.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618bd30881909e54d0708f144786 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.