Triple
T18548485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jivajirao Scindia |
E453300
|
entity |
| Predicate | officeStartAsRajpramukhOfMadhyaBharat |
P132105
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Jivajirao Scindia, officeStartAsRajpramukhOfMadhyaBharat, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartAsRajpramukhOfMadhyaBharat Context triple: [Jivajirao Scindia, officeStartAsRajpramukhOfMadhyaBharat, 1948]
-
A.
officeStart (Chief Minister of Uttar Pradesh)
Indicates the date or point in time when the person became the Chief Minister of Uttar Pradesh.
-
B.
firstRajpramukh
Indicates that the subject is the first person to hold the position or title of Rajpramukh.
-
C.
officeStartAsMinisterOfNativeAffairs
Indicates the point in time when an individual begins serving in the role of Minister of Native Affairs.
-
D.
termStartAsGovernorGeneralOfIndia
Indicates the date or point in time when an individual began their tenure as Governor-General of India.
-
E.
officeStartTime (Governor of Madras)
Indicates the time at which the Governor of Madras officially began their term in office.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534be2298819095f637065fc2724e |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.