Triple

T33725298
Position Surface form Disambiguated ID Type / Status
Subject Cheluvi E864126 entity
Predicate hasScreenwriterRole P80863 FINISHED
Object Girish Karnad 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: Girish Karnad | Statement: [Cheluvi, hasScreenwriterRole, Girish Karnad]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasScreenwriterRole
Context triple: [Cheluvi, hasScreenwriterRole, Girish Karnad]
  • A. hasScreenwriter
    Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
  • B. hasScreenwriterCreator chosen
    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. screenwriterOfWorkAppearingIn
    Indicates that a person is the screenwriter of a work in which a specified entity (such as a character, actor, or role) appears.
  • 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.

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_69f3498a64cc8190b4b414c67b280d93 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: May 1, 2026, 1:44 a.m.