Triple
T8669303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagdeep Dhankhar |
E205754
|
entity |
| Predicate | RajasthanAssemblyTermEnd |
P83990
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Jagdeep Dhankhar, RajasthanAssemblyTermEnd, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RajasthanAssemblyTermEnd Context triple: [Jagdeep Dhankhar, RajasthanAssemblyTermEnd, 1998]
-
A.
rajyaSabhaTermStart
Indicates the date on which an individual's term as a member of the Rajya Sabha (the upper house of India's Parliament) begins.
-
B.
termEndAsGovernorGeneralOfIndia
Indicates the date or point in time when an individual’s tenure as Governor-General of India came to an end.
-
C.
unionTerritoryPeriod
Indicates the time span during which an entity held the status of a union territory.
-
D.
chairedInRajyaSabhaBy
Indicates that a particular session, meeting, or proceeding in the Rajya Sabha was presided over or chaired by a specified individual.
-
E.
fourthTermAsChiefMinisterEnd
Indicates the date or point in time when an entity’s fourth term serving as Chief Minister comes to an end.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4917cb9881909a73b74e54250613 |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.