Triple
T516521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lok Sabha |
E10720
|
entity |
| Predicate | electoralSystemType |
P539
|
FINISHED |
| Object | direct 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: direct election | Statement: [Lok Sabha, electoralSystemType, direct election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralSystemType Context triple: [Lok Sabha, electoralSystemType, direct election]
-
A.
electionMethod
chosen
Indicates the process or system used to select a candidate or make a decision in an election.
-
B.
electionSystemFeature
Indicates that an election system possesses a specific characteristic, mechanism, or procedural feature related to how elections are conducted or managed.
-
C.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
D.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
E.
electoralBasis
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f184c3a481909bf60bb627b0ea88 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.