Triple
T34460474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihariganj Assembly constituency |
E884623
|
entity |
| Predicate | hasPollingSystem |
P199154
|
FINISHED |
| Object | single-member constituency |
—
|
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: single-member constituency | Statement: [Bihariganj Assembly constituency, hasPollingSystem, single-member constituency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPollingSystem Context triple: [Bihariganj Assembly constituency, hasPollingSystem, single-member constituency]
-
A.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
-
B.
hasStateSystem
Indicates that an entity possesses, follows, or is governed by a particular system of state organization, rules, or governance.
-
C.
hasCentralSystem
Indicates that an entity possesses or is associated with a primary controlling or coordinating system at its core.
-
D.
hasJobSystem
Indicates that an entity is associated with or operates under a particular job or employment system.
-
E.
hasPrimarySystem
Indicates that an entity is associated with or operates under a main or principal system among potentially multiple systems.
- F. None of above. chosen
Provenance (4 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69ff234e63648190a7b09a161029c8e2 |
completed | May 9, 2026, 12:06 p.m. |
Created at: May 1, 2026, 2 a.m.