Triple
T21992532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uttar Pradesh |
E509513
|
entity |
| Predicate | hasRajyaSabhaSeats |
P20744
|
FINISHED |
| Object | 31 |
—
|
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: 31 | Statement: [Uttar Pradesh, hasRajyaSabhaSeats, 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRajyaSabhaSeats Context triple: [Uttar Pradesh, hasRajyaSabhaSeats, 31]
-
A.
RajyaSabhaSeats
chosen
Indicates the number of seats allocated or held in the Rajya Sabha (the upper house of the Indian Parliament) within a given political or administrative context.
-
B.
LokSabhaSeats
Indicates the number of seats a political party or entity holds or is allocated in the Lok Sabha (the lower house of India’s Parliament).
-
C.
hasLegislativeChamberSeats
Indicates that a legislative chamber holds or is allocated a specified number of seats.
-
D.
hasSeatsForConstituency
Indicates that a governing body or institution allocates or provides a certain number of representative seats for a specific constituency.
-
E.
legislativeCouncilSeats
Indicates the number of seats held or allocated in a legislative council within a given political or administrative 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1270e951081908deda039b47ca84b |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:15 p.m.