Triple
T13036156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kima Ventures |
E326564
|
entity |
| Predicate | sectorAgnostic |
P20324
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kima Ventures, sectorAgnostic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorAgnostic Context triple: [Kima Ventures, sectorAgnostic, true]
-
A.
sectorBase
Indicates that one entity serves as the primary base or foundational location for operations within a particular sector of another entity.
-
B.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
C.
sectorNeutral
chosen
Indicates that the relationship or action is independent of, or unaffected by, the specific sector or industry of the entities involved.
-
D.
sectorPreparation
Indicates that an entity is involved in getting a specific sector ready for operation, use, or transition through planning, setup, or related preparatory actions.
-
E.
sectorRecognized
Indicates that an entity has been formally acknowledged or classified within a particular sector or industry.
- 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.