Triple
T21888902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen in Council |
E540484
|
entity |
| Predicate | exercisesPowerType |
P123612
|
FINISHED |
| Object | executive authority |
—
|
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: executive authority | Statement: [Queen in Council, exercisesPowerType, executive authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisesPowerType Context triple: [Queen in Council, exercisesPowerType, executive authority]
-
A.
exercisesPowerInNameOf
Indicates that one entity wields authority or influence on behalf of, and under the authorization or representation of, another entity.
-
B.
exercisesPowersOf
Indicates that one entity actively uses, applies, or carries out the authority, rights, or powers granted to it over or in relation to another entity.
-
C.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
D.
coreExercise
Indicates that an exercise primarily targets and engages the muscles of the core or midsection.
-
E.
involvesPowerType
chosen
Indicates that the relationship or action is associated with, characterized by, or dependent on a specific type or category of power.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ef2b648190bbd78f6b3958d2ee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.