Triple
T37646552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSE All Shares Index |
E937052
|
entity |
| Predicate | includesClosedEndFunds |
P30088
|
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, includesClosedEndFunds, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesClosedEndFunds Context triple: [PSE All Shares Index, includesClosedEndFunds, false]
-
A.
includesFundType
chosen
Indicates that one entity contains or encompasses a particular type or category of fund within its scope or structure.
-
B.
includesInvestmentVehicles
Indicates that one entity contains, comprises, or makes use of specific investment vehicles as part of its structure or offerings.
-
C.
isIndexFund
Indicates that an investment fund is structured to track a specific market index rather than actively selecting individual securities.
-
D.
isIncludedInGlobalFinancialETFs
Indicates that an entity is a constituent holding within one or more globally focused financial exchange-traded funds (ETFs).
-
E.
isUsedInIndexFunds
Indicates that something serves as a component or instrument within index fund investment strategies.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.