Triple

T30763170
Position Surface form Disambiguated ID Type / Status
Subject The Lamentation of Doctor Faustus E783290 entity
Predicate hasFictionalComposer P68311 FINISHED
Object Adrian Leverkühn 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: Adrian Leverkühn | Statement: [The Lamentation of Doctor Faustus, hasFictionalComposer, Adrian Leverkühn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalComposer
Context triple: [The Lamentation of Doctor Faustus, hasFictionalComposer, Adrian Leverkühn]
  • A. hasMusicalComposer
    Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
  • B. hasFictionalSong
    Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
  • C. hasFictionalAuthor chosen
    Indicates that one entity is the fictional or in-universe author of a work attributed to them.
  • D. hasFictionalPerformer
    Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
  • E. hasNotableComposer
    Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
  • 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_69f224b047f48190b4f5efeb7ee97b37 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe1fd637c08190aa95cd2478c278cb completed May 8, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69fe19344bb481909b5e2144155e4add completed May 8, 2026, 5:11 p.m.
Created at: April 29, 2026, 8:39 p.m.