Triple
T17883251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyta Hall |
E447141
|
entity |
| Predicate | emotionallyCharacterizedBy |
P76175
|
FINISHED |
| Object | intense grief |
—
|
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: intense grief | Statement: [Lyta Hall, emotionallyCharacterizedBy, intense grief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionallyCharacterizedBy Context triple: [Lyta Hall, emotionallyCharacterizedBy, intense grief]
-
A.
emotionalTrait
Indicates that an entity possesses a particular emotional characteristic, disposition, or affective quality.
-
B.
emotionalCounterpartOf
Indicates that one entity serves as the emotional equivalent, complement, or matching emotional role of another entity.
-
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.
emotionState
chosen
Indicates the emotional condition or feeling that an entity is currently experiencing.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c1016508190857adce1a0fbb355 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.