Triple

T22541502
Position Surface form Disambiguated ID Type / Status
Subject Spoon River E557299 entity
Predicate inspiredLiteraryForm P6480 FINISHED
Object dramatic monologue 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: dramatic monologue | Statement: [Spoon River, inspiredLiteraryForm, dramatic monologue]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inspiredLiteraryForm
Context triple: [Spoon River, inspiredLiteraryForm, dramatic monologue]
  • A. hasLiteraryForm chosen
    Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
  • B. literaryMuseOf
    Indicates a relationship in which one entity serves as the creative inspiration or muse for another entity’s literary work.
  • C. literaryInfluence
    Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
  • D. inspiredDocument
    Indicates that one entity (often a work, idea, or person) served as the creative or conceptual inspiration for the creation or content of another document.
  • E. literaryFeature
    Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
  • 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_69e11e58662081909ae346ab384514ca completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15f3251808190a72b849157854d8d completed April 29, 2026, 1:30 a.m.
PD Predicate disambiguation batch_69e898c864148190a3f5feec7967d49c completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:51 p.m.