Triple
T8076870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX |
E188513
|
entity |
| Predicate | hasUnderlyingCompanyStockCodeOnTSE |
P57989
|
FINISHED |
| Object | 8591 |
—
|
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: 8591 | Statement: [IX, hasUnderlyingCompanyStockCodeOnTSE, 8591]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingCompanyStockCodeOnTSE Context triple: [IX, hasUnderlyingCompanyStockCodeOnTSE, 8591]
-
A.
underlyingCompanyTicker
chosen
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
-
B.
underlyingCompanyExchange
Indicates that one entity is the stock exchange on which the underlying company of another financial instrument or contract is listed or traded.
-
C.
underlyingCompanyPrimaryListingTicker
Indicates the stock ticker symbol of the primary exchange listing for the underlying company.
-
D.
issuerStockExchangeCode
Indicates the stock exchange code where the issuer’s securities are listed or traded.
-
E.
hasUnderlyingCompanyPrimaryListing
Indicates that an entity is associated with the company where that company’s primary stock exchange listing is held.
- F. None of above.
Provenance (3 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a184488190b19ef7066f0f5057 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.