Triple

T35226264
Position Surface form Disambiguated ID Type / Status
Subject Mark Peploe E1017103 entity
Predicate hasGenreAsScreenwriter P195014 FINISHED
Object historical drama 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: historical drama | Statement: [Mark Peploe, hasGenreAsScreenwriter, historical drama]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGenreAsScreenwriter
Context triple: [Mark Peploe, hasGenreAsScreenwriter, historical drama]
  • A. hasScreenwriter
    Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
  • B. hasScreenwriterCreator
    Indicates that an entity has another entity serving as the screenwriter who created or originated its screenplay.
  • C. screenwriterOfContainingFilm
    Indicates that one entity is the screenwriter who wrote the screenplay for a film in which the other entity is contained (e.g., as a segment, episode, or part).
  • D. hasDirectorScreenwriter
    Indicates that a director is also the screenwriter (or one of the screenwriters) for a given work.
  • E. associatedWithScreenwriter
    Indicates a relationship in which an entity is connected or linked to a screenwriter, typically through collaboration, authorship, or professional involvement in a screenwriting context.
  • F. None of above. chosen

Provenance (4 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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd974d75e08190af46b1d608769f3b completed May 8, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69fd94ff792c8190bedf4a639d3da809 completed May 8, 2026, 7:47 a.m.
PDg Predicate description generation batch_69fd974c0e8481909fdd312897c647b3 completed May 8, 2026, 7:57 a.m.
Created at: May 3, 2026, 4:02 p.m.