Triple
T308833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of India |
E6358
|
entity |
| Predicate | maximumStrengthRajyaSabha |
P7799
|
FINISHED |
| Object | 250 members |
—
|
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: 250 members | Statement: [Parliament of India, maximumStrengthRajyaSabha, 250 members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumStrengthRajyaSabha Context triple: [Parliament of India, maximumStrengthRajyaSabha, 250 members]
-
A.
numberOfRepresentatives
Indicates the quantity of representatives associated with a given entity or unit.
-
B.
totalNumberOfLegislators
chosen
Indicates the total count of legislators associated with a given political body, jurisdiction, or legislative session.
-
C.
numberOfMinistersLimit
Indicates a constraint specifying the maximum allowable number of ministers in a given context or governing body.
-
D.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
E.
areRepresentedIn
Indicates that one entity serves as a representation, depiction, or encoding of another entity within a given medium, context, or system.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea33ba688190b30d285cd7aa0d82 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93f38308190b4b480c951f1a1c3 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.