Triple
T33599364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark (Love Actually) |
E860672
|
entity |
| Predicate | confessesLoveTo |
P40219
|
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), confessesLoveTo, Juliet (Love Actually)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confessesLoveTo Context triple: [Mark (Love Actually), confessesLoveTo, Juliet (Love Actually)]
-
A.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
B.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
C.
confesses
chosen
Indicates that one entity openly admits or acknowledges something, typically a wrongdoing, secret, or previously concealed fact, to another entity.
-
D.
rumoredLoverOf
Indicates that one entity is widely believed or speculated to be the romantic partner or lover of another entity, without confirmed evidence.
-
E.
fellInLoveWith
Indicates that one entity developed romantic love or deep affectionate feelings 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_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:41 a.m.