Triple
T26870673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingate Global Fund |
E676601
|
entity |
| Predicate | typeOfInvestors |
P29189
|
FINISHED |
| Object | high-net-worth individuals |
—
|
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: high-net-worth individuals | Statement: [Kingate Global Fund, typeOfInvestors, high-net-worth individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfInvestors Context triple: [Kingate Global Fund, typeOfInvestors, high-net-worth individuals]
-
A.
typeOfInvestor
chosen
Indicates the kind or category of investor that a given entity is classified as.
-
B.
investorTargetGroup
Indicates that a particular group or segment is the intended or primary focus of investment efforts or strategies.
-
C.
allowsInvestorType
Indicates that an entity permits or accepts a specified type or category of investor.
-
D.
targetInvestorNeed
Indicates that an action, product, or communication is specifically aimed at addressing or fulfilling an investor’s particular needs or requirements.
-
E.
coInvestorsIncluded
Indicates that specified co-investors are included as part of a particular investment, deal, or financial arrangement.
- 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_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 27, 2026, 5:32 a.m.