Triple
T1369309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orders of Council |
E30074
|
entity |
| Predicate | authorisedBy |
P2246
|
FINISHED |
| Object | Royal prerogative |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Royal prerogative | Statement: [Orders of Council, authorisedBy, Royal prerogative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorisedBy Context triple: [Orders of Council, authorisedBy, Royal prerogative]
-
A.
reauthorizedBy
Indicates that an existing authorization, approval, or mandate has been renewed or extended by a specific agent or authority.
-
B.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
C.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
D.
grantedBy
chosen
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
E.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
- F. None of above.
Provenance (3 batches)
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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d60fdc8190a9954b74ca2b2541 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.