Triple
T37646553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSE All Shares Index |
E937052
|
entity |
| Predicate | includesDepositaryReceipts |
P206019
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [PSE All Shares Index, includesDepositaryReceipts, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDepositaryReceipts Context triple: [PSE All Shares Index, includesDepositaryReceipts, false]
-
A.
allowsDepositaryReceipts
Indicates that an entity permits the issuance or listing of depositary receipts representing underlying securities.
-
B.
hasGlobalDepositaryReceipts
Indicates that an entity has issued or is associated with global depositary receipts representing its underlying securities in international markets.
-
C.
includesSecurities
Indicates that one entity contains or comprises one or more securities as part of its composition or holdings.
-
D.
includesDividends
Indicates that the referenced value or calculation already accounts for dividend payments in its total.
-
E.
isIncludedInCanadianEquityETFs
Indicates that an entity is a constituent holding within one or more Canadian equity exchange-traded funds.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.