Triple
T26870636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tremont Group feeder funds |
E676600
|
entity |
| Predicate | assetClassLabel |
P161974
|
FINISHED |
| Object | alternative investments |
—
|
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: alternative investments | Statement: [Tremont Group feeder funds, assetClassLabel, alternative investments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetClassLabel Context triple: [Tremont Group feeder funds, assetClassLabel, alternative investments]
-
A.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
B.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
C.
assetClassesTraded
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
D.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
E.
instrumentClassification
Indicates that one entity is classified as a particular type or category of instrument in relation to another entity.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:32 a.m.