Triple
T2516561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deputy Chairman of Rajya Sabha |
E55424
|
entity |
| Predicate | decisionOnPointsOfOrder |
P2273
|
FINISHED |
| Object | final |
—
|
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: final | Statement: [Deputy Chairman of Rajya Sabha, decisionOnPointsOfOrder, final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionOnPointsOfOrder Context triple: [Deputy Chairman of Rajya Sabha, decisionOnPointsOfOrder, final]
-
A.
decidesOn
chosen
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
B.
adoptedRulesOfProcedureOn
Indicates that an entity formally established or approved rules of procedure on a specific date or occasion.
-
C.
decisionBody
Indicates that one entity serves as the authoritative body or group responsible for making a particular decision regarding another entity or matter.
-
D.
votingOrder
Indicates the sequence or priority in which entities cast their votes or have their votes considered.
-
E.
presidingOfficerVoteException
Indicates an exception to the usual voting rules that allows the presiding officer to cast a vote under specific circumstances.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.