Triple
T32310648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajya Sabha constituencies of India |
E825488
|
entity |
| Predicate | allocatesSeatsTo |
P174167
|
FINISHED |
| Object | Indian states |
—
|
NE NERFINISHED |
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: Indian states | Statement: [Rajya Sabha constituencies of India, allocatesSeatsTo, Indian states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatesSeatsTo Context triple: [Rajya Sabha constituencies of India, allocatesSeatsTo, Indian states]
-
A.
seatsAreAllocatedTo
Indicates that specific seats are assigned or designated to particular entities (such as people, groups, or bookings).
-
B.
seatsAllocatedBy
Indicates that seats are assigned or distributed by a particular agent, authority, or mechanism.
-
C.
remainingSeatsAllocation
Indicates how any seats that are still unassigned after an initial distribution are allocated among eligible parties or entities.
-
D.
seatsForParty
Indicates that a seating arrangement or capacity is designated to accommodate a specific party or group.
-
E.
seatAllocationLevel
Indicates the degree or priority level at which seats are assigned or distributed among eligible entities.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb69574819082ba3ff1072d8301 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:46 a.m.