Triple
T22526678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuri Zhivago |
E556922
|
entity |
| Predicate | loveStoryCharacterizedAs |
P122100
|
FINISHED |
| Object | tragic |
—
|
LITERAL FINISHED |
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: tragic | Statement: [Yuri Zhivago, loveStoryCharacterizedAs, tragic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loveStoryCharacterizedAs Context triple: [Yuri Zhivago, loveStoryCharacterizedAs, tragic]
-
A.
romanticSubplotCentral
Indicates that a romantic subplot is a primary, driving element of the narrative rather than a minor or peripheral thread.
-
B.
protagonistLover
Indicates that one entity is the romantic partner or love interest of the story’s protagonist.
-
C.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
D.
storyCharacterizedAs
chosen
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
E.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed352b48190a96ef2896f2978cd |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:51 p.m.