Triple
T3780506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greylock Partners |
E85404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | private partnership |
C1882
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: private partnership Context triple: [Greylock Partners, instanceOf, private partnership]
-
A.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
-
B.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
C.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
D.
limited partnership
chosen
A limited partnership is a business structure in which at least one general partner manages the business and bears unlimited liability, while one or more limited partners contribute capital and have liability limited to their investment with no role in day-to-day management.
-
E.
human partnership
A human partnership is a collaborative relationship between two or more people who share goals, responsibilities, and mutual support to achieve common outcomes.
- F. None of above.
Provenance (1 batch)
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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:12 p.m.