Triple
T34652621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priol |
E889877
|
entity |
| Predicate | isUnderElectionCommission |
P157000
|
FINISHED |
| Object | Election Commission of India |
—
|
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: Election Commission of India | Statement: [Priol, isUnderElectionCommission, Election Commission of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnderElectionCommission Context triple: [Priol, isUnderElectionCommission, Election Commission of India]
-
A.
hasElectionCommission
chosen
Indicates that an entity is associated with, governed by, or overseen by a specific election commission.
-
B.
isElectedFor
Indicates that an entity attains a position, role, or office as the result of an election for that specific position.
-
C.
isElectoralOffice
Indicates that the referenced position or role is an official public office filled through an electoral process.
-
D.
isElectedRepresentative
Indicates that a person holds a public office or position as a result of being chosen through an election by eligible voters.
-
E.
statusWithElectionCommission
Indicates the formal standing or condition of an entity as recorded or recognized by an election commission.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c4fd388190a269f97bb31e6656 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.