Triple
T13859440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research and Information Service |
E333150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parliamentary research service |
C8702
|
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 research service Context triple: [Research and Information Service, instanceOf, parliamentary research service]
-
A.
parliamentary service
chosen
Parliamentary service is the professional support and administrative work carried out to assist a parliament in its legislative, oversight, and representative functions.
-
B.
parliamentary paper
A parliamentary paper is an official document produced or presented to a legislature, typically containing reports, proposals, evidence, or records used to inform and support parliamentary debate and decision-making.
-
C.
parliamentary record
A parliamentary record is an official, authoritative written or transcribed account of the proceedings, debates, decisions, and votes that occur within a parliamentary body.
-
D.
component_of_parliament
A component_of_parliament is an institutional or structural subdivision (such as a chamber, committee, or office) that forms part of the overall parliamentary system and contributes to its legislative, deliberative, or oversight functions.
-
E.
parliamentary network
A parliamentary network is a structured system of relationships and interactions among legislators, parties, committees, and external stakeholders that facilitates the flow of information, influence, and decision-making within and around a parliament.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:14 p.m.