Triple
T37359225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porgi, amor |
E927533
|
entity |
| Predicate | expressesFeeling |
P35317
|
FINISHED |
| Object | longing for emotional relief |
—
|
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: longing for emotional relief | Statement: [Porgi, amor, expressesFeeling, longing for emotional relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressesFeeling Context triple: [Porgi, amor, expressesFeeling, longing for emotional relief]
-
A.
expressesEmotionThrough
Indicates that one entity conveys or manifests an emotion by means of another entity (such as an action, medium, or expression).
-
B.
feels
chosen
Indicates that an entity experiences or has a particular emotion, sensation, or internal state in relation to something.
-
C.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
D.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.