Triple

T15693360
Position Surface form Disambiguated ID Type / Status
Subject Alcestis E380389 entity
Predicate literaryTypeRole P15535 FINISHED
Object tragic heroine 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 heroine | Statement: [Alcestis, literaryTypeRole, tragic heroine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: literaryTypeRole
Context triple: [Alcestis, literaryTypeRole, tragic heroine]
  • A. literaryRole chosen
    Indicates the specific narrative or functional role an entity holds within a literary work or text.
  • B. literaryThemeInvolvement
    Indicates the involvement or presence of a particular literary theme within a work, passage, or character arc.
  • C. genreRole
    Indicates a relationship where an entity holds a specific functional or categorical role within a particular genre.
  • D. literaryGenreOfWork
    Indicates that a work belongs to or is classified under a particular literary genre.
  • E. dramaticStructureRole
    Indicates the specific function or role an element plays within the overall dramatic structure of a narrative or performance.
  • 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_69d86d99e860819094b6957cde470f2c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b4d6b5788190883746ee82c799f5 completed April 16, 2026, 10:07 a.m.
PD Predicate disambiguation batch_69e0051d639481909a10614e8f83e659 completed April 15, 2026, 9:37 p.m.
Created at: April 10, 2026, 4:44 a.m.