Triple
T23023988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summertime |
E573247
|
entity |
| Predicate | romanticInterestCharacter |
P143936
|
FINISHED |
| Object | Renato de Rossi |
—
|
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: Renato de Rossi | Statement: [Summertime, romanticInterestCharacter, Renato de Rossi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticInterestCharacter Context triple: [Summertime, romanticInterestCharacter, Renato de Rossi]
-
A.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
B.
romanticPartnerInSeries
chosen
Indicates that one character is portrayed as a romantic partner of another character within the context of a specific series or narrative.
-
C.
protagonistLover
Indicates that one entity is the romantic partner or love interest of the story’s protagonist.
-
D.
romanticPartnerRealName
Indicates that the real, non-alias name of a person is associated with someone who is their romantic partner.
-
E.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847b86688190b678d0d09ecd3c3d |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.