Triple
T23680744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament Secretariat of Singapore |
E585010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parliamentary administrative body |
C45575
|
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: parliamentary administrative body Context triple: [Parliament Secretariat of Singapore, instanceOf, parliamentary administrative body]
-
A.
parliamentary bureau
chosen
A parliamentary bureau is the administrative and coordinating body within a parliament responsible for organizing its internal functioning, managing legislative procedures, and supporting the work of its members and leadership.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
internal administrative body
An internal administrative body is an organized group within an institution responsible for managing, coordinating, and overseeing its internal operations, policies, and support functions.
-
D.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
E.
cabinet-level body
A cabinet-level body is a high-ranking executive group, typically composed of heads of major government departments and key advisors, that assists a head of state or government in making and implementing national policy decisions.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:51 p.m.