Triple
T25171018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XTSE |
E630321
|
entity |
| Predicate | identifiesTradingVenue |
P158196
|
FINISHED |
| Object | Toronto Stock Exchange |
—
|
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: Toronto Stock Exchange | Statement: [XTSE, identifiesTradingVenue, Toronto Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesTradingVenue Context triple: [XTSE, identifiesTradingVenue, Toronto Stock Exchange]
-
A.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
B.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
C.
hasTradingVenueCode
Indicates that an entity is associated with a specific trading venue through its designated code.
-
D.
isMarketCentreFor
Indicates that one location functions as the primary marketplace or commercial hub serving another area or community.
-
E.
mainStockExchangeOf
Indicates that one entity serves as the primary stock exchange on which the other entity (typically a company or financial instrument) is chiefly listed or traded.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d467e6c8190a328ee6b07aef240 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 12:20 p.m.