Triple
T33599358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark (Love Actually) |
E860672
|
entity |
| Predicate | hasUnspokenFeelingsFor |
P140327
|
FINISHED |
| Object | Juliet (Love Actually) |
—
|
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: Juliet (Love Actually) | Statement: [Mark (Love Actually), hasUnspokenFeelingsFor, Juliet (Love Actually)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnspokenFeelingsFor Context triple: [Mark (Love Actually), hasUnspokenFeelingsFor, Juliet (Love Actually)]
-
A.
hidesFeelings
Indicates that one entity deliberately conceals or suppresses their emotions or emotional state from others.
-
B.
hasRumoredSubtext
Indicates that something is believed or speculated to contain an implied or hidden meaning that is not explicitly stated.
-
C.
hasRepressedDesireFor
Indicates that one entity harbors a hidden or unacknowledged longing or attraction toward another entity.
-
D.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
E.
romanticFeeling
chosen
Indicates that one entity experiences romantic attraction or affection toward 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 1:41 a.m.