Triple
T433079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajya Sabha |
E9754
|
entity |
| Predicate | cannotIntroduce |
P13900
|
FINISHED |
| Object | Money bills |
—
|
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: Money bills | Statement: [Rajya Sabha, cannotIntroduce, Money bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotIntroduce Context triple: [Rajya Sabha, cannotIntroduce, Money bills]
-
A.
canIntroduce
Indicates that one entity has the ability or permission to introduce another entity to a third party or context.
-
B.
cannotReview
Indicates that an entity is not permitted or able to perform a review of another entity or item.
-
C.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
D.
cannotBeAmendedInRespectOf
Indicates that a particular item (such as a term, provision, or condition) is not allowed to be changed or modified in the specified respect or aspect.
-
E.
notRecognizedBy
Indicates that one entity does not acknowledge, accept, or formally recognize the status, authority, or validity of another entity.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef084840819080653004b674cba8 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edda55e88190b7c17ba94d7df1ce |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb93584819082f23eff13e17c4f |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.