Triple
T15206160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devi Lal |
E363393
|
entity |
| Predicate | termStartAsDeputyPrimeMinisterOfIndia |
P24150
|
FINISHED |
| Object | 1989 |
—
|
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 | Statement: [Devi Lal, termStartAsDeputyPrimeMinisterOfIndia, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsDeputyPrimeMinisterOfIndia Context triple: [Devi Lal, termStartAsDeputyPrimeMinisterOfIndia, 1989]
-
A.
deputyPrimeMinisterStart
chosen
Indicates the date or point in time when an individual begins serving in the role of deputy prime minister.
-
B.
endTimeAsDeputyPrimeMinister
Indicates the date and time at which an individual’s tenure in the role of Deputy Prime Minister comes to an end.
-
C.
resultedInDeputyPrimeMinister
Indicates that one entity’s action, decision, or event caused or led to another entity becoming Deputy Prime Minister.
-
D.
termStartAsViceroyOfIndia
Indicates the date or point in time when an individual began serving in the role of Viceroy of India.
-
E.
termStartAsGovernorGeneralOfIndia
Indicates the date or point in time when an individual began their tenure as Governor-General of India.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b7964c8190bc8dc3444b94f15e |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:11 a.m.