Triple
T18737946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhairon Singh Shekhawat |
E458212
|
entity |
| Predicate | chiefMinisterTerm |
P133358
|
FINISHED |
| Object | 1977-06-22 to 1980-02-16 |
—
|
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: 1977-06-22 to 1980-02-16 | Statement: [Bhairon Singh Shekhawat, chiefMinisterTerm, 1977-06-22 to 1980-02-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefMinisterTerm Context triple: [Bhairon Singh Shekhawat, chiefMinisterTerm, 1977-06-22 to 1980-02-16]
-
A.
primeMinisterTerm
Indicates the period of time during which a person holds the office and exercises the role of prime minister of a government.
-
B.
primeMinisterTermStart
Indicates the date on which an individual officially begins serving as prime minister.
-
C.
primeMinisterTermEnd
Indicates the date or point in time when a person's tenure as prime minister comes to an end.
-
D.
numberOfTermsAsChiefMinister
Indicates the count of separate terms an individual has served in the role of Chief Minister.
-
E.
firstTermAsChiefMinisterEnd
Indicates the date or point in time when an entity’s first term serving as Chief Minister came 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768b80ac8190bc05628d64f86fc9 |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.