Triple
T6668963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters Patent, 1947 |
E151676
|
entity |
| Predicate | affectsPowersOf |
P8541
|
FINISHED |
| Object | monarch of Canada |
—
|
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: monarch of Canada | Statement: [Letters Patent, 1947, affectsPowersOf, monarch of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsPowersOf Context triple: [Letters Patent, 1947, affectsPowersOf, monarch of Canada]
-
A.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
-
B.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
definesPowersOf
chosen
Indicates that one entity specifies or determines the scope, limits, or nature of the authority or powers held by another entity.
-
E.
involvedPower
Indicates that a particular power, authority, or state is a participant or actor in the referenced event, situation, or relationship.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.