Triple
T13036171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kima Ventures |
E326564
|
entity |
| Predicate | portfolioDiversity |
P14738
|
FINISHED |
| Object | multi-sector |
—
|
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: multi-sector | Statement: [Kima Ventures, portfolioDiversity, multi-sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portfolioDiversity Context triple: [Kima Ventures, portfolioDiversity, multi-sector]
-
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.
diversifiedIn
chosen
Indicates that an entity has expanded its involvement, investments, or activities across multiple different areas, sectors, or asset types.
-
C.
portfolioOf
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
D.
folio
Indicates that one entity is a specific page, leaf, or numbered side within a larger bound or paginated document associated with another entity.
-
E.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:55 p.m.