Triple
T36689593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashok Gehlot |
E905919
|
entity |
| Predicate | termStartAsChiefMinister |
P83666
|
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: [Ashok Gehlot, termStartAsChiefMinister, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsChiefMinister Context triple: [Ashok Gehlot, termStartAsChiefMinister, 1998]
-
A.
termStartAsMinisterGeneral
Indicates the date or point in time when an individual begins serving in the role of Minister General.
-
B.
termAsMinisterStart
Indicates the date or point in time when an individual begins serving in a specific ministerial position.
-
C.
firstTermAsChiefMinisterStart
chosen
Indicates the date or time when an individual’s first term serving as Chief Minister began.
-
D.
termStartAsActingPrimeMinister
Indicates that a person’s term in office begins specifically in the capacity of acting prime minister, rather than as a fully appointed or elected prime minister.
-
E.
termStartAsDeputyMinister
Indicates that an individual began their term in office serving in the role of Deputy Minister.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.