Triple
T30996765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Jaime |
E789821
|
entity |
| Predicate | romanticOrSexualFixationOn |
P121194
|
FINISHED |
| Object | Viridiana |
—
|
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: Viridiana | Statement: [Don Jaime, romanticOrSexualFixationOn, Viridiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticOrSexualFixationOn Context triple: [Don Jaime, romanticOrSexualFixationOn, Viridiana]
-
A.
obsessionWith
Indicates an intense, persistent, and often overwhelming preoccupation or fixation that one entity has toward another entity or object.
-
B.
romanticallyObsessedWith
chosen
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
C.
romanticManipulationOf
Indicates a relationship where one entity deliberately exploits romantic feelings or dynamics to control, influence, or deceive another entity.
-
D.
coneSex
Indicates a sexual or mating relationship involving a cone-shaped structure or entity.
-
E.
objectOfAffectionFor
Indicates that one entity is the target or recipient of another entity’s romantic or affectionate feelings.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 8:56 p.m.