Triple
T18673421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clearlake Capital |
E456537
|
entity |
| Predicate | portfolioCompanySector |
P59909
|
FINISHED |
| Object | enterprise software |
—
|
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: enterprise software | Statement: [Clearlake Capital, portfolioCompanySector, enterprise software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portfolioCompanySector Context triple: [Clearlake Capital, portfolioCompanySector, enterprise software]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
portfolioCompany
Indicates that one entity is a company in which another entity (typically an investor or investment fund) holds an ownership stake as part of its investment portfolio.
-
C.
targetCompanyIndustry
chosen
Indicates that a company operates within or is associated with a specified industry sector.
-
D.
technologySectorFeature
Indicates that something is a characteristic, attribute, or defining aspect of the technology sector.
-
E.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b41cd881908f37bf7c85e96559 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.