Triple
T26870632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tremont Group feeder funds |
E676600
|
entity |
| Predicate | domicileType |
P161547
|
FINISHED |
| Object | offshore and onshore fund structures |
—
|
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: offshore and onshore fund structures | Statement: [Tremont Group feeder funds, domicileType, offshore and onshore fund structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domicileType Context triple: [Tremont Group feeder funds, domicileType, offshore and onshore fund structures]
-
A.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
B.
domicile
Indicates that one entity serves as the legal or habitual residence or home location of another entity.
-
C.
typeOfHouse
Indicates the specific category or kind of house associated with an entity (e.g., apartment, detached house, townhouse).
-
D.
isDwelling
Indicates that one entity serves as a residence or living place for another entity.
-
E.
propertyType_id
Indicates a relationship that specifies the type or category of a property associated with an 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_69f61e9b57bc8190a262eb0203f9dd3f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 5:32 a.m.