Triple
T27594652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jodhpur Lok Sabha constituency |
E699861
|
entity |
| Predicate | currentMPFromElectionYear |
P186952
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Jodhpur Lok Sabha constituency, currentMPFromElectionYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMPFromElectionYear Context triple: [Jodhpur Lok Sabha constituency, currentMPFromElectionYear, 2014]
-
A.
currentMP
Indicates that the subject is the person who currently serves as a Member of Parliament representing the object’s constituency or jurisdiction.
-
B.
previousMPStartYear
Indicates the year in which the subject’s immediately preceding term as a Member of Parliament began.
-
C.
targetedOfficeElectionYear
Indicates the year in which the election is held for the office that is the target of the relationship.
-
D.
currentIncumbentStartYear
Indicates the year in which the entity’s current incumbent began their tenure or term in that role.
-
E.
currentLegislatureStartYear
Indicates the calendar year in which the currently serving legislature (or legislative term) officially began.
- F. None of above. chosen
Provenance (4 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: April 27, 2026, 2:06 p.m.