Triple
T7013161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P Asia 50 |
E162632
|
entity |
| Predicate | includesAssetClass |
P28209
|
FINISHED |
| Object | equities |
—
|
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: equities | Statement: [S&P Asia 50, includesAssetClass, equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAssetClass Context triple: [S&P Asia 50, includesAssetClass, equities]
-
A.
coversAssetClass
chosen
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
B.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
C.
assetClassesTraded
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
D.
includesFundType
Indicates that one entity contains or encompasses a particular type or category of fund within its scope or structure.
-
E.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc58b04c8190af4913dbaf43c3d4 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:34 p.m.