Triple
T21998378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finance Bill (India) |
E543261
|
entity |
| Predicate | timeLimitInRajyaSabha |
P50361
|
FINISHED |
| Object | 14 days |
—
|
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: 14 days | Statement: [Finance Bill (India), timeLimitInRajyaSabha, 14 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLimitInRajyaSabha Context triple: [Finance Bill (India), timeLimitInRajyaSabha, 14 days]
-
A.
datePassedInRajyaSabha
Indicates that a proposed bill or motion has been approved by a vote in the Rajya Sabha (the upper house of the Indian Parliament).
-
B.
rajyaSabhaTermStart
Indicates the date on which an individual's term as a member of the Rajya Sabha (the upper house of India's Parliament) begins.
-
C.
timeLimitForRatification
chosen
Indicates the deadline or maximum period allowed for an agreement, decision, or act to be formally ratified.
-
D.
maximumDurationOfParliamentSessionPerYear
Indicates the longest allowable length of time that a parliament is permitted to be in session within a single year.
-
E.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276774508190b96870266e10979a |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.