Triple

T28264437
Position Surface form Disambiguated ID Type / Status
Subject Flipkart E712661 entity
Predicate roleOfKalyanKrishnamurthy P164667 FINISHED
Object Chief Executive Officer 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: Chief Executive Officer | Statement: [Flipkart, roleOfKalyanKrishnamurthy, Chief Executive Officer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleOfKalyanKrishnamurthy
Context triple: [Flipkart, roleOfKalyanKrishnamurthy, Chief Executive Officer]
  • A. roleInRamakrishnaMovement
    Indicates that an entity holds or has held a specific role or function within the Ramakrishna Movement.
  • B. roleInKrishnaLife
    Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
  • C. roleOfVarunKrishna
    Indicates that an entity holds the role, position, or function associated with Varun Krishna.
  • D. roleInGaudiyaVaishnavism
    Indicates the specific function, position, or significance an entity holds within the theological, devotional, or institutional framework of Gaudiya Vaishnavism.
  • E. Deepak SehgalIs
    Indicates that an entity is identified as or characterized by the person Deepak Sehgal.
  • 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_69efb5216c6881908020dce4aea65381 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f64ee0c2788190a94a04ad1902fd5e completed May 2, 2026, 7:22 p.m.
PD Predicate disambiguation batch_69f64caede108190a35cc7cbfead866f completed May 2, 2026, 7:12 p.m.
PDg Predicate description generation batch_69f64e36c57c8190af09470a8d35512b completed May 2, 2026, 7:19 p.m.
Created at: April 27, 2026, 11:13 p.m.