Triple
T27799743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana Legislative Assembly |
E702206
|
entity |
| Predicate | subsequentElectionHeldInYear |
P126021
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Telangana Legislative Assembly, subsequentElectionHeldInYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentElectionHeldInYear Context triple: [Telangana Legislative Assembly, subsequentElectionHeldInYear, 2018]
-
A.
reElectionYear
Indicates the year in which an entity is (or is scheduled to be) elected again to the same position or office.
-
B.
nextElectionYear
chosen
Indicates the calendar year in which the subsequent scheduled election for the referenced office, jurisdiction, or entity is to take place.
-
C.
previousElectionYear
Indicates the year in which the immediately preceding election for the same office, position, or body took place.
-
D.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
-
E.
electionsHeldOn
Indicates that one or more elections took place on a specified date or set of dates.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5:33 p.m.