Triple
T23571146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Product Officer of Stripe |
E580114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | C‑level position |
C337
|
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: C‑level position Context triple: [Chief Product Officer of Stripe, instanceOf, C‑level position]
-
A.
entry-level position
An entry-level position is a job role designed for individuals with minimal professional experience, providing foundational responsibilities, training, and opportunities to develop skills in a particular field or industry.
-
B.
senior clerical rank
A senior clerical rank is a high-level position within a religious or administrative hierarchy, typically involving significant authority, oversight responsibilities, and decision-making power over lower-ranking clerical roles.
-
C.
supervisory position
A supervisory position is a role in which an individual oversees the work of others, ensuring tasks are completed effectively while providing guidance, support, and performance management.
-
D.
executive position
chosen
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
-
E.
senior engineering position
A senior engineering position is a high-level technical role responsible for leading complex projects, making architectural decisions, mentoring other engineers, and driving engineering best practices to deliver robust, scalable solutions.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:36 p.m.