Triple
T31095121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lok Sabha constituency |
E792502
|
entity |
| Predicate | hasPollingUnits |
P152393
|
FINISHED |
| Object | polling stations |
—
|
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: polling stations | Statement: [Lok Sabha constituency, hasPollingUnits, polling stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPollingUnits Context triple: [Lok Sabha constituency, hasPollingUnits, polling stations]
-
A.
havePollingStations
chosen
Indicates that one entity possesses, hosts, or is assigned a set of polling stations for conducting an election or vote.
-
B.
hasPollingDivisionCode
Indicates that an entity is associated with a specific polling division identified by a particular code.
-
C.
hasElectoralDistricts
Indicates that a political or administrative unit is divided into one or more electoral districts used for representation or voting.
-
D.
hasElectoralUnit
Indicates that a political or administrative entity is associated with a specific electoral unit used for voting or representation.
-
E.
hasNumberOfConstituencies
Indicates the specific count of constituencies associated with an entity.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 29, 2026, 9:03 p.m.