Triple
T19426996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chariclo |
E486003
|
entity |
| Predicate | emotionInMyth |
P87208
|
FINISHED |
| Object | grief for Actaeon |
—
|
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: grief for Actaeon | Statement: [Chariclo, emotionInMyth, grief for Actaeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionInMyth Context triple: [Chariclo, emotionInMyth, grief for Actaeon]
-
A.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
B.
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).
-
C.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
D.
emotionalCoreOf
Indicates that one entity serves as the central source, essence, or primary driver of another entity’s emotional character or experience.
-
E.
emotionalTrait
chosen
Indicates that an entity possesses a particular emotional characteristic, disposition, or affective quality.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63219f27481909fe686209defc971 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.