Triple

T5134789
Position Surface form Disambiguated ID Type / Status
Subject Meghnad Saha E115793 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. Mangal
    Mangal is a given name most notably borne by Mangal Pandey, an Indian soldier whose actions helped spark the Indian Rebellion of 1857.
  • D. Varuna
    Varuna is a large, rapidly rotating trans-Neptunian object in the Kuiper Belt, notable for its elongated shape and classification as a likely dwarf-planet candidate.
  • E. Varuna
    Varuna is an ancient Vedic god primarily associated with cosmic order, moral law, and the waters, often regarded as a sovereign guardian of ṛta (universal order).
  • 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_69bd44459a988190a772a5c2ec6a1965 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd784e306081908dd8317227227807 completed March 20, 2026, 4:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69bec4cd5e188190b1404cefc887e0b3 completed March 21, 2026, 4:18 p.m.
Created at: March 20, 2026, 1:43 p.m.