Triple
T35456855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurmukh Nihal Singh |
E1024797
|
entity |
| Predicate | endTimeAsChiefMinisterOfDelhi |
P126581
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [Gurmukh Nihal Singh, endTimeAsChiefMinisterOfDelhi, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeAsChiefMinisterOfDelhi Context triple: [Gurmukh Nihal Singh, endTimeAsChiefMinisterOfDelhi, 1955]
-
A.
termEndAsChiefMinisterOfDelhi
chosen
Indicates the time period during which an individual’s tenure serving as the Chief Minister of Delhi comes to an end.
-
B.
termEndAsChiefMinisterOfHaryana
Indicates the point in time when an individual's tenure serving as Chief Minister of Haryana concludes.
-
C.
succeededByAsChiefMinisterOfDelhi
Indicates that one person directly followed another in holding the position of Chief Minister of Delhi.
-
D.
precededByAsChiefMinisterOfDelhi
Indicates that one individual previously held the position of Chief Minister of Delhi immediately before another individual.
-
E.
inceptionAsChiefMinisterOfDelhi
Indicates the event or point in time when an individual assumes office as the Chief Minister of Delhi.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 3, 2026, 4:04 p.m.