Triple
T18945667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Madhya Pradesh Legislative Assembly election |
E463505
|
entity |
| Predicate | termLengthOfAssembly |
P33746
|
FINISHED |
| Object | 5 years |
—
|
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: 5 years | Statement: [2018 Madhya Pradesh Legislative Assembly election, termLengthOfAssembly, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termLengthOfAssembly Context triple: [2018 Madhya Pradesh Legislative Assembly election, termLengthOfAssembly, 5 years]
-
A.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
termLengthNumber
chosen
Indicates the numerical value representing the duration or length of a specified term.
-
C.
termLengthCharacteristic
Indicates the specific duration-related property or feature associated with a term (such as its length or time span).
-
D.
parliamentaryTerm
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
-
E.
electsTermLength
Indicates the length of time for which an entity is elected to hold a particular position or office.
- 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.