Triple
T2460773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajasthan Legislative Assembly |
E54527
|
entity |
| Predicate | lastElectionYear |
P3713
|
FINISHED |
| Object | 2023 |
—
|
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 | Statement: [Rajasthan Legislative Assembly, lastElectionYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastElectionYear Context triple: [Rajasthan Legislative Assembly, lastElectionYear, 2023]
-
A.
lastElection
chosen
Indicates the most recent electoral event associated with an entity, such as the latest election in which it participated or was affected.
-
B.
reElectionYear
Indicates the year in which an entity is (or is scheduled to be) elected again to the same position or office.
-
C.
targetedOfficeElectionYear
Indicates the year in which the election is held for the office that is the target of the relationship.
-
D.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
E.
houseElectionsHeld
Indicates that elections have been conducted to choose members of a legislative house or lower chamber.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.