Triple
T12844108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angela Beesley |
E307127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | web entrepreneur |
C5238
|
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: web entrepreneur Context triple: [Angela Beesley, instanceOf, web 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.
business owner
A business owner is an individual or entity that creates, controls, and is ultimately responsible for the strategic direction, operations, and financial outcomes of a business.
-
C.
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.
-
D.
blogging platform operator
chosen
A blogging platform operator is an entity responsible for providing, maintaining, and governing the technical infrastructure and policies that enable users to create, publish, manage, and distribute blog content online.
-
E.
real estate entrepreneur
A real estate entrepreneur is an individual who identifies, acquires, develops, and manages property-based opportunities to generate profit and build long-term value through strategic investment and innovation in the real estate market.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:36 p.m.