Triple
T6180007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Bank of Canada |
E137917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | company listed on the New York Stock Exchange |
C17773
|
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: company listed on the New York Stock Exchange Context triple: [Royal Bank of Canada, instanceOf, company listed on the New York Stock Exchange]
-
A.
company listed on the Toronto Stock Exchange
chosen
A company listed on the Toronto Stock Exchange is a publicly traded corporation that meets TSX listing requirements and whose shares are bought and sold on the Toronto Stock Exchange marketplace.
-
B.
market segment of the London Stock Exchange
A market segment of the London Stock Exchange is a defined subdivision of the exchange that groups securities with similar characteristics, regulatory requirements, and trading rules to facilitate organized listing and trading.
-
C.
stock exchange
A stock exchange is an organized marketplace where securities such as stocks and bonds are listed, bought, and sold under regulated rules and procedures.
-
D.
sub-market of the London Stock Exchange
A sub-market of the London Stock Exchange is a distinct segment within the broader exchange that groups companies or securities based on specific criteria such as size, sector, regulatory requirements, or listing standards.
-
E.
publicly traded holding company
A publicly traded holding company is a corporation whose primary business is owning controlling interests in other companies, with its shares available for purchase on public stock exchanges.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:18 p.m.