Triple
T20336308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Investment |
E492619
|
entity |
| Predicate | portfolioSectorExposure |
P5739
|
FINISHED |
| Object | hospitality |
—
|
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: hospitality | Statement: [Cascade Investment, portfolioSectorExposure, hospitality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portfolioSectorExposure Context triple: [Cascade Investment, portfolioSectorExposure, hospitality]
-
A.
portfolioConcentration
Indicates the degree to which investments or holdings are focused in a limited number of assets, sectors, or strategies within a portfolio.
-
B.
portfolioWithin
Indicates that one portfolio is contained within, or is a subset of, another portfolio.
-
C.
sectorInfluence
Indicates the degree to which one sector affects, shapes, or exerts control over another sector or over outcomes within that sector.
-
D.
sectorWeighting
chosen
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
-
E.
marketPortfolioProxy
Indicates that one entity serves as a proxy or representative approximation of the overall market portfolio for another entity or context.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677eb4d5881908ea5ec5a1dd7eafa |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.