Triple
T26870611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tremont Group feeder funds |
E676600
|
entity |
| Predicate | lostAssets |
P20740
|
FINISHED |
| Object | billions of US dollars in client funds |
—
|
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: billions of US dollars in client funds | Statement: [Tremont Group feeder funds, lostAssets, billions of US dollars in client funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostAssets Context triple: [Tremont Group feeder funds, lostAssets, billions of US dollars in client funds]
-
A.
lostOrDestroyed
Indicates that something has ceased to exist in its original, usable form, either by being misplaced beyond recovery or physically destroyed.
-
B.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
C.
lostSettlement
Indicates that a settlement previously possessed by an entity has been relinquished or is no longer under that entity’s control.
-
D.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
E.
lost
chosen
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e9b57bc8190a262eb0203f9dd3f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:32 a.m.