Triple
T32256439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabby Gabby |
E824037
|
entity |
| Predicate | receivesAffectionFrom |
P61253
|
FINISHED |
| Object | Harmony (attempted) |
—
|
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: Harmony (attempted) | Statement: [Gabby Gabby, receivesAffectionFrom, Harmony (attempted)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesAffectionFrom Context triple: [Gabby Gabby, receivesAffectionFrom, Harmony (attempted)]
-
A.
affectionReciprocated
Indicates that feelings of affection expressed by one entity toward another are mutually returned by the other entity.
-
B.
competesForAffectionWith
Indicates a relationship where two or more entities vie against each other to gain the affection or emotional favor of the same target entity.
-
C.
objectOfAffectionFor
Indicates that one entity is the target or recipient of another entity’s romantic or affectionate feelings.
-
D.
hasAffectionateUse
Indicates that one entity uses or refers to another in a loving, tender, or emotionally warm manner.
-
E.
isBelovedOf
chosen
Indicates that one entity is deeply loved, cherished, or held in special affection by another entity.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 12:41 a.m.