Triple
T22118389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non-constituency Member of Parliament scheme |
E546598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | feature of Singapore Parliament |
C28645
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: feature of Singapore Parliament Context triple: [Non-constituency Member of Parliament scheme, instanceOf, feature of Singapore Parliament]
-
A.
parliamentary institution feature
chosen
A parliamentary institution feature is a structural or procedural element—such as committees, question periods, voting rules, or leadership roles—that shapes how a parliament organizes its work, makes decisions, and holds the government accountable.
-
B.
Act of Parliament of Singapore
An Act of Parliament of Singapore is a written law formally enacted by the Singapore Parliament, receiving Presidential assent and forming part of the nation’s primary legislation.
-
C.
chamber of Parliament of Malaysia
A chamber of Parliament of Malaysia is one of the two separate legislative houses—the Dewan Rakyat (House of Representatives) or the Dewan Negara (Senate)—where elected or appointed members meet to debate, amend, and pass federal laws.
-
D.
seat of a lower house of parliament
A seat of a lower house of parliament is an individual position held by an elected or appointed representative in the primary legislative chamber responsible for initiating and debating laws.
-
E.
seat of a legislature
The seat of a legislature is the designated city or location where a legislative body officially convenes to conduct its sessions and carry out its formal duties.
- F. None of above.
Provenance (1 batch)
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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.