Triple

T9111188
Position Surface form Disambiguated ID Type / Status
Subject Doctor Faustus (opera) E218602 entity
Predicate narrativeOutcomeForProtagonist P86129 FINISHED
Object damnation — 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: damnation | Statement: [Doctor Faustus (opera), narrativeOutcomeForProtagonist, damnation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: narrativeOutcomeForProtagonist
Context triple: [Doctor Faustus (opera), narrativeOutcomeForProtagonist, damnation]
  • A. hasNarrativeOutcome chosen
    Indicates that an event, action, or narrative element leads to or results in a particular story-related consequence or resolution.
  • B. narrativeConsequence
    Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
  • C. narrativeGoal
    Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
  • D. describesOutcomeOf
    Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
  • E. outcomeOf
    Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
  • 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_69ca83dc94ac8190b9ef42684d36ff39 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca847102881908f9d86ce9883fb1a completed April 1, 2026, 5:08 a.m.
PD Predicate disambiguation batch_69cc65fe5be081909d4470d6317b14a6 completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:16 p.m.