Triple
T24783246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granny Weatherwax |
E620055
|
entity |
| Predicate | formerRomanticInterest |
P162062
|
FINISHED |
| Object | Mustrum Ridcully |
—
|
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: Mustrum Ridcully | Statement: [Granny Weatherwax, formerRomanticInterest, Mustrum Ridcully]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRomanticInterest Context triple: [Granny Weatherwax, formerRomanticInterest, Mustrum Ridcully]
-
A.
romanticInterestInAnotherTimeline
Indicates that one entity has or expresses romantic interest toward another entity specifically within an alternate or different timeline.
-
B.
romanticPartnerRealName
Indicates that the real, non-alias name of a person is associated with someone who is their romantic partner.
-
C.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
D.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
E.
protagonistLover
Indicates that one entity is the romantic partner or love interest of the story’s protagonist.
- F. None of above. chosen
Provenance (4 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 18, 2026, 4:45 a.m.