Triple
T26227087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultanpur Lok Sabha constituency |
E655920
|
entity |
| Predicate | termOfOfficeForMP |
P17403
|
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: [Sultanpur Lok Sabha constituency, termOfOfficeForMP, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termOfOfficeForMP Context triple: [Sultanpur Lok Sabha constituency, termOfOfficeForMP, 5 years]
-
A.
parliamentaryTerm
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
-
B.
parliamentaryTermDependent
Indicates that the existence, duration, or validity of something is contingent upon the length or continuation of a parliamentary term.
-
C.
numberOfTermInOffice
Indicates the specific ordinal count of how many terms an entity has served in a particular office or position.
-
D.
termInOffice
chosen
Indicates the period during which an individual officially holds a particular office or position.
-
E.
parliamentaryTermType
Indicates the specific category or classification of a parliamentary term within a legislative or governmental context.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d54f9cc8190adecacaf86a4c639 |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:58 p.m.