Triple
T14388946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Curry |
E356792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer entrepreneur |
C17
|
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: computer entrepreneur Context triple: [Chris Curry, instanceOf, computer entrepreneur]
-
A.
software entrepreneur
A software entrepreneur is an individual who identifies market needs and builds, launches, and scales software-based products or services, assuming financial and strategic risk to create a sustainable business.
-
B.
high-tech entrepreneur
A high-tech entrepreneur is an individual who identifies innovative opportunities in advanced technologies and builds scalable, technology-driven ventures to bring those innovations to market.
-
C.
telecommunications entrepreneur
A telecommunications entrepreneur is an individual who identifies opportunities and builds businesses that develop, provide, or innovate communication networks, services, or technologies connecting people and organizations.
-
D.
information technology pioneer
chosen
An information technology pioneer is an individual who significantly advances the development, application, or understanding of computing and digital technologies, often introducing groundbreaking concepts, systems, or practices that shape the evolution of the IT field.
-
E.
cybersecurity entrepreneur
A cybersecurity entrepreneur is an individual who identifies digital security risks and market needs, then builds and scales innovative security-focused products or services to protect organizations and users from cyber threats.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.