Triple
T1766001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal prerogative of the United Kingdom |
E38764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | set of executive powers |
C416
|
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: set of executive powers Context triple: [Royal prerogative of the United Kingdom, instanceOf, set of executive powers]
-
A.
executive authority
chosen
Executive authority is the power and responsibility to implement, enforce, and administer laws and policies within a governing system or organization.
-
B.
executive order
An executive order is a formal directive issued by a head of the executive branch, such as a president or governor, that manages operations of the government and has the force of law within the scope of existing statutory or constitutional authority.
-
C.
presidential administration
A presidential administration is the organized body of officials, agencies, and policies led by a president during their term in office, responsible for executing and managing the functions of the executive branch of government.
-
D.
supreme state authority
The supreme state authority is the highest governing body or institution within a state that holds ultimate legal and political power to make, interpret, and enforce binding decisions over its territory and population.
-
E.
executive position
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.