Triple
T27180142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calisto |
E683168
|
entity |
| Predicate | hasMainLoveInterest |
P176284
|
FINISHED |
| Object | Melibea |
—
|
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: Melibea | Statement: [Calisto, hasMainLoveInterest, Melibea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLoveInterest Context triple: [Calisto, hasMainLoveInterest, Melibea]
-
A.
hasFictionalRomanticInterest
Indicates that one entity is portrayed as having a romantic attraction or interest toward another entity within a fictional context.
-
B.
hasYoungLoverCharacter
Indicates that an entity is involved in a romantic or intimate relationship with a significantly younger lover character.
-
C.
formerRomanticInterest
Indicates that one entity previously had a romantic relationship or attraction toward another entity, but that romantic connection has since ended.
-
D.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
E.
hasRomanticEntanglementInPlot
chosen
Indicates that a romantic relationship or involvement between characters is a significant element within the narrative plot.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 27, 2026, 9:28 a.m.