Triple
T34392317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Reason to Love |
E882735
|
entity |
| Predicate | inspiresObsessionOf |
P49999
|
FINISHED |
| Object | Betty Sizemore |
—
|
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: Betty Sizemore | Statement: [A Reason to Love, inspiresObsessionOf, Betty Sizemore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiresObsessionOf Context triple: [A Reason to Love, inspiresObsessionOf, Betty Sizemore]
-
A.
obsessionWith
chosen
Indicates an intense, persistent, and often overwhelming preoccupation or fixation that one entity has toward another entity or object.
-
B.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
C.
inspiredDedicationOf
Indicates that one entity’s dedication, commitment, or devoted effort is motivated, sparked, or strengthened by another entity.
-
D.
protagonistFascination
Indicates a strong, often central interest or captivation that the protagonist feels toward someone, something, or some subject.
-
E.
inspiredEmotion
Indicates that one entity has caused or stimulated a particular emotion or emotional state in 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:59 a.m.