Triple
T18945666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Madhya Pradesh Legislative Assembly election |
E463505
|
entity |
| Predicate | termStartOfAssembly |
P94662
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [2018 Madhya Pradesh Legislative Assembly election, termStartOfAssembly, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartOfAssembly Context triple: [2018 Madhya Pradesh Legislative Assembly election, termStartOfAssembly, 2019]
-
A.
termStartAsAssemblyMember
Indicates that an individual begins a term of service in the role of an assembly member.
-
B.
termStartOfCaliforniaAssemblyService
Indicates the date on which an individual’s term of service in the California State Assembly begins.
-
C.
parliamentaryTermStarted
chosen
Indicates that a specific parliamentary term has begun for a legislative body or member.
-
D.
termStartAsStateRepresentative
Indicates the date or event when an individual begins serving in office as a state representative.
-
E.
startOfCurrentApportionment
Indicates the point in time when the current apportionment period or allocation arrangement begins.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d53f6eb8819099b1268db8b14d66 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.