Triple
T6180060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Bank of Canada |
E137917
|
entity |
| Predicate | mainRegulatoryFiling |
P69516
|
FINISHED |
| Object | annual report |
—
|
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: annual report | Statement: [Royal Bank of Canada, mainRegulatoryFiling, annual report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRegulatoryFiling Context triple: [Royal Bank of Canada, mainRegulatoryFiling, annual report]
-
A.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
-
B.
regulatoryForm
Indicates the specific legal or organizational regulatory structure under which an entity is established or operates.
-
C.
hasSECFilingsURL
Indicates that there is a URL linking an entity to its filings or disclosure documents submitted to the U.S. Securities and Exchange Commission (SEC).
-
D.
regulatoryField
Indicates that one entity operates within, is governed by, or is associated with a particular area or domain of regulation defined by another entity.
-
E.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
- F. None of above. chosen
Provenance (4 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c060fca4cc8190bf95231cd2a594c1 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.