Triple
T23680608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giasone |
E585006
|
entity |
| Predicate | hasPrologueCharacter |
P152970
|
FINISHED |
| Object | Amore (Cupid) |
—
|
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: Amore (Cupid) | Statement: [Giasone, hasPrologueCharacter, Amore (Cupid)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrologueCharacter Context triple: [Giasone, hasPrologueCharacter, Amore (Cupid)]
-
A.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
-
B.
hasPrologueSetting
Indicates that the setting specified is the location or context in which the prologue of a work takes place.
-
C.
hasPrologueInTitle
Indicates that a work’s title explicitly includes the word “Prologue” or a prologue-related phrase.
-
D.
hasPrologueTheme
Indicates that a work’s prologue centers on, introduces, or is characterized by a particular thematic content or motif.
-
E.
hasPrologueSeries
Indicates that one work serves as a prologue or introductory installment to another work in a series.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f835ec8190a7bdcfa48ad79cd5 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.