Triple
T25847567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishwanath Pratap Singh |
E651114
|
entity |
| Predicate | termStartAsPrimeMinisterOfIndia |
P370
|
FINISHED |
| Object | 1989-12-02 |
—
|
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: 1989-12-02 | Statement: [Vishwanath Pratap Singh, termStartAsPrimeMinisterOfIndia, 1989-12-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsPrimeMinisterOfIndia Context triple: [Vishwanath Pratap Singh, termStartAsPrimeMinisterOfIndia, 1989-12-02]
-
A.
termStartAsGovernorGeneralOfIndia
Indicates the date or point in time when an individual began their tenure as Governor-General of India.
-
B.
primeMinisterTermStart
chosen
Indicates the date on which an individual officially begins serving as prime minister.
-
C.
startTimeAsChiefJusticeOfIndia
Indicates the date and time at which an individual begins serving in the role of Chief Justice of India.
-
D.
termStartAsViceroyOfIndia
Indicates the date or point in time when an individual began serving in the role of Viceroy of India.
-
E.
primeMinisterAtStart
Indicates that the subject was serving as prime minister at the beginning of a specified period or event.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602392a048190ae5ac8ebf09a3f45 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:57 a.m.