Triple

T20477608
Position Surface form Disambiguated ID Type / Status
Subject Rajendra Singh E502359 entity
Predicate officeAssumedAsSarsanghchalak P72481 FINISHED
Object 1994 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: 1994 | Statement: [Rajendra Singh, officeAssumedAsSarsanghchalak, 1994]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: officeAssumedAsSarsanghchalak
Context triple: [Rajendra Singh, officeAssumedAsSarsanghchalak, 1994]
  • A. officeStartAsMinisterOfNativeAffairs
    Indicates the point in time when an individual begins serving in the role of Minister of Native Affairs.
  • B. startTimeAsSarsanghchalak chosen
    Indicates the point in time at which an individual began serving in the role of Sarsanghchalak.
  • C. officeStart (Chief Minister of Uttar Pradesh)
    Indicates the date or point in time when the person became the Chief Minister of Uttar Pradesh.
  • D. officeEnd (Chief Minister of Uttar Pradesh)
    Indicates the date or point in time when the person’s tenure as Chief Minister of Uttar Pradesh comes to an end.
  • E. becamePracharakOf
    Indicates that one entity assumed the role or position of a pracharak (propagator/missionary worker) associated with another entity, such as an organization or movement.
  • 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_69e0b4af32848190aea80682b44d5d6e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69966b9748190a5296d8ab03c07a1 completed April 20, 2026, 9:23 p.m.
PD Predicate disambiguation batch_69e5768372988190b08ef8ae67d42ab6 completed April 20, 2026, 12:42 a.m.
Created at: April 16, 2026, 11:34 a.m.