Triple
T38541486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSX:TPX.B |
E924843
|
entity |
| Predicate | associatedCompanyStockExchangeListing |
P206519
|
FINISHED |
| Object | NYSE:TAP |
E924842
|
NE 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: NYSE:TAP | Statement: [TSX:TPX.B, associatedCompanyStockExchangeListing, NYSE:TAP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyStockExchangeListing Context triple: [TSX:TPX.B, associatedCompanyStockExchangeListing, NYSE:TAP]
-
A.
hasParentStockExchangeListing
Indicates that an entity’s stock exchange listing is derived from, or associated with, the listing of its parent company on a stock exchange.
-
B.
ownerStockExchangeListing
Indicates that a stock exchange on which an entity is listed is owned or operated by another entity.
-
C.
parentCompanyListedOn
Indicates that the parent company of an entity is publicly listed on a particular stock exchange or market.
-
D.
stockExchangeListingOfSubsidiary
Indicates that a subsidiary company is listed and traded on a particular stock exchange.
-
E.
stockListedThrough
Indicates that a company’s stock is made available for public trading via a specific stock exchange or listing mechanism.
- F. None of above. chosen
Provenance (5 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41f430eb248190befef915b01ea498 |
completed | June 29, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.