Triple
T26311605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmad |
E661839
|
entity |
| Predicate | providesEmotionalThroughlineIn |
P86972
|
FINISHED |
| Object | Soul Food |
—
|
NE NERFINISHED |
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: Soul Food | Statement: [Ahmad, providesEmotionalThroughlineIn, Soul Food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesEmotionalThroughlineIn Context triple: [Ahmad, providesEmotionalThroughlineIn, Soul Food]
-
A.
emotionalTrajectory
Indicates how an entity’s emotional state changes or progresses over time in relation to another entity or context.
-
B.
emotionalCoreOf
chosen
Indicates that one entity serves as the central source, essence, or primary driver of another entity’s emotional character or experience.
-
C.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
D.
emotionalRole
Indicates a relationship where one entity holds a particular emotional significance, function, or impact in relation to another entity.
-
E.
emotionalScope
Indicates the range or extent of emotions involved or affected within a given relationship or situation.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 26, 2026, 10:22 p.m.