Triple
T32310642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajya Sabha constituencies of India |
E825488
|
entity |
| Predicate | hasElectorType |
P38956
|
FINISHED |
| Object | indirect election |
—
|
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: indirect election | Statement: [Rajya Sabha constituencies of India, hasElectorType, indirect election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectorType Context triple: [Rajya Sabha constituencies of India, hasElectorType, indirect election]
-
A.
hasElectionType
Indicates the specific category or kind of election associated with a given electoral event or process.
-
B.
hasElectorCount
Indicates that an entity is associated with a specific number of electors or electoral votes.
-
C.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
-
D.
hasTypeOfVoters
chosen
Indicates that an entity is associated with or characterized by a particular category or kind of voters.
-
E.
hasElectoralRollType
Indicates the specific category or type of electoral roll associated with an entity, such as general, special, or supplementary voter lists.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 12:46 a.m.