Triple
T32393909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitoge Kirisaki |
E827749
|
entity |
| Predicate | canonicalLoveInterest |
P7325
|
FINISHED |
| Object | Raku Ichijou |
—
|
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: Raku Ichijou | Statement: [Chitoge Kirisaki, canonicalLoveInterest, Raku Ichijou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalLoveInterest Context triple: [Chitoge Kirisaki, canonicalLoveInterest, Raku Ichijou]
-
A.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
B.
loveInterest
chosen
Indicates that one entity is the romantic object of affection or attraction for another entity.
-
C.
loveInterestType
Indicates the specific kind or category of romantic or affectionate relationship that exists between the related entities.
-
D.
formerRomanticInterest
Indicates that one entity previously had a romantic relationship or attraction toward another entity, but that romantic connection has since ended.
-
E.
hasLoveInterestInWork
Indicates that one entity is portrayed as a romantic love interest of another entity within a specific creative work.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:52 a.m.