Triple
T18837792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 Madhya Pradesh Legislative Assembly election |
E460709
|
entity |
| Predicate | voteCountingDate |
P108125
|
FINISHED |
| Object | 2023-12-03 |
—
|
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: 2023-12-03 | Statement: [2023 Madhya Pradesh Legislative Assembly election, voteCountingDate, 2023-12-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteCountingDate Context triple: [2023 Madhya Pradesh Legislative Assembly election, voteCountingDate, 2023-12-03]
-
A.
voteCountingStartDate
Indicates the date on which the process of counting votes is scheduled to begin.
-
B.
electoralVoteCountingDate
chosen
Indicates the date on which electoral votes are formally counted or tallied in an election process.
-
C.
voteCountingCompletedOn
Indicates that the process of counting votes for a particular election or decision was fully completed on a specific date or time.
-
D.
electorCountDate
Indicates the date on which the number of electors (or electoral votes) associated with an entity is determined or recorded.
-
E.
voteResultAnnouncementDate
Indicates the date on which the outcome of a vote is officially announced.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99f443881909516a82208fd0178 |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.