Triple
T9770936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silchar Assembly constituency |
E237120
|
entity |
| Predicate | languageUsedInElections |
P9260
|
FINISHED |
| Object | Assamese |
—
|
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: Assamese | Statement: [Silchar Assembly constituency, languageUsedInElections, Assamese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInElections Context triple: [Silchar Assembly constituency, languageUsedInElections, Assamese]
-
A.
languageOfBallots
chosen
Indicates the language or languages in which ballots are written or presented.
-
B.
languageOfCampaigning
Indicates the language used to conduct or communicate a campaign (e.g., political, marketing, or advocacy efforts).
-
C.
languageOfLegislature
Indicates the language or languages officially used by a legislature to conduct its proceedings, draft laws, and perform its formal functions.
-
D.
lawGoverningElection
Indicates that a specified law regulates or provides the legal framework for conducting a particular election.
-
E.
electoralPattern
Indicates a recurring or characteristic way in which elections or voting outcomes tend to occur or be distributed across contexts.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f329148190a5e531478bc18073 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.