Triple
T20431791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bank of Nova Scotia |
E501148
|
entity |
| Predicate | tradesAs |
P10476
|
FINISHED |
| Object | BNS on TSX |
—
|
NE NERFINISHED |
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: BNS on TSX | Statement: [The Bank of Nova Scotia, tradesAs, BNS on TSX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BNS on TSX Context triple: [The Bank of Nova Scotia, tradesAs, BNS on TSX]
-
A.
BNS (NYSE)
BNS (NYSE) is the stock ticker symbol for The Bank of Nova Scotia, one of Canada's largest multinational banks.
-
B.
TSX
TSX is a TypeScript-based extension of JSX that allows developers to write strongly typed, XML-like syntax for defining user interfaces in frameworks like React.
-
C.
BNS
chosen
BNS is the stock ticker symbol for the Bank of Nova Scotia, one of Canada’s largest multinational banks.
-
D.
BNS
BNS is the main national multipurpose sports stadium in Dhaka, Bangladesh, historically used for major football and cricket events.
-
E.
BNX
BNX is the IATA airport code for Banja Luka International Airport in Bosnia and Herzegovina.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685eaa4c8819083d1d7aee0f998a6 |
completed | April 20, 2026, 8 p.m. |
Created at: April 16, 2026, 11:31 a.m.