Triple
T17299683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Executive Officer of Oracle Corporation |
E420008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | executiveManagementPosition |
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: executiveManagementPosition Context triple: [Chief Executive Officer of Oracle Corporation, instanceOf, executiveManagementPosition]
-
A.
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.
-
B.
executive office-holder
An executive office-holder is an individual who occupies a formal position of authority within an organization or government, empowered to make and implement decisions, manage operations, and represent the entity in official capacities.
-
C.
executive leaders
Executive leaders are high-level organizational decision-makers who set strategic direction, allocate critical resources, and influence culture and performance across the enterprise.
-
D.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
E.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:41 a.m.