Triple

T19411648
Position Surface form Disambiguated ID Type / Status
Subject Tripathi E485600 entity
Predicate hasVariant P455 FINISHED
Object Tripathy 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: Tripathy | Statement: [Tripathi, hasVariant, Tripathy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tripathy
Context triple: [Tripathi, hasVariant, Tripathy]
  • A. Tripathi chosen
    Tripathi is an Indian-origin surname commonly associated with Hindu Brahmin communities, particularly in northern India.
  • B. Parthasarathy
    Parthasarathy is an Indian surname commonly found among South Indian communities, often associated with Tamil and Telugu speakers.
  • C. Chattopadhyay
    Chattopadhyay is a Bengali surname notably borne by influential Indian writer Sarat Chandra Chattopadhyay, renowned for his socially conscious novels and stories.
  • D. Swarup
    Swarup is an Indian given name commonly used for males, derived from Sanskrit and generally meaning "form" or "true nature."
  • E. Pradip
    Pradip is a masculine given name commonly used in India and among people of Indian origin.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62af681288190ba2ec52d5adb6a22 completed April 20, 2026, 1:32 p.m.
Created at: April 10, 2026, 1:37 p.m.