Triple

T29558388
Position Surface form Disambiguated ID Type / Status
Subject Kireedam E749967 entity
Predicate starsNotableActor P5563 FINISHED
Object Ajith Kumar 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: Ajith Kumar | Statement: [Kireedam, starsNotableActor, Ajith Kumar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: starsNotableActor
Context triple: [Kireedam, starsNotableActor, Ajith Kumar]
  • A. notableStar
    Indicates that the subject is a star (or stellar object) that is distinguished or noteworthy in some significant way, such as brightness, fame, or scientific interest, relative to other stars.
  • B. starredActor chosen
    Indicates that an actor performed a leading or significant role in a particular production or work.
  • C. notableWorkStar
    Indicates that a particular work (such as a film, show, or production) is one of the notable works in which the specified star (person) prominently appears or performs.
  • D. notableStarName
    Indicates that the subject is known by the specified star name as a notable or prominent designation.
  • E. notableCastFeature
    Indicates that a cast member has a distinctive or noteworthy characteristic, role, or attribute that is especially significant in the context of the production.
  • 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_69f0bd4919e48190942b2a13d5b97d03 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66d1b59e481908e7a4676160788c0 completed May 2, 2026, 9:31 p.m.
PD Predicate disambiguation batch_69f6633ac8a88190ab0cda62bbfcf9b0 completed May 2, 2026, 8:48 p.m.
Created at: April 28, 2026, 5:18 p.m.