Triple

T10807521
Position Surface form Disambiguated ID Type / Status
Subject Meghnad Saha E255006 entity
Predicate familyName P18 FINISHED
Object Saha E255007 NE 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: Saha | Statement: [Meghnad Saha, familyName, Saha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saha
Context triple: [Meghnad Saha, familyName, Saha]
  • A. Saha
    Saha is a small town in the Ambala district of the northern Indian state of Haryana, known primarily as a local commercial and transport hub for surrounding rural areas.
  • B. Saha chosen
    Saha is a surname most notably associated with Indian astrophysicist Meghnad Saha, known for the Saha ionization equation in stellar astrophysics.
  • C. Sedov
    Sedov is a Russian surname most notably associated with Lev Sedov, the revolutionary son of Leon Trotsky.
  • D. Sahodhari
    Sahodhari is an Indian Tamil-language film produced by the prominent Chennai-based studio AVM Productions.
  • E. Mangal
    Mangal is a Pashtun tribe traditionally associated with the Karlani tribal confederation in Afghanistan and Pakistan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa61c15c8190a1839550c56e75e1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d733b506488190921e6a1f4168dd9e completed April 9, 2026, 5:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69de8513fe0881909d6833c85aac03a8 completed April 14, 2026, 6:19 p.m.
Created at: April 8, 2026, 9:18 p.m.