Triple
T23627616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APF |
E583511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Parliamentary organization |
C47888
|
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 organization Context triple: [APF, instanceOf, Parliamentary organization]
-
A.
parliamentary institution feature
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.
legislative body
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
C.
organ of the Assembly of the Republic
An organ of the Assembly of the Republic is an institutional body or structural component within the Assembly that performs specific legislative, administrative, or oversight functions to support its constitutional role.
-
D.
parliamentary party grouping
A parliamentary party grouping is an organized coalition of legislators within a parliament who share a common political affiliation or agenda and act collectively to influence legislation and policy.
-
E.
organ of the Scottish Parliament
An organ of the Scottish Parliament is an official body or component institution that forms part of the Parliament’s structure and is responsible for carrying out specific legislative, administrative, or oversight functions within the Scottish parliamentary system.
- F. None of above. chosen
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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:46 p.m.