Triple
T5127482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle iProcurement |
E115618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | self-service procurement application |
C10206
|
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: self-service procurement application Context triple: [Oracle iProcurement, instanceOf, self-service procurement application]
-
A.
procurement management initiative
A procurement management initiative is a coordinated effort to optimize how an organization plans, sources, negotiates, and manages the acquisition of goods and services to reduce costs, improve quality, and ensure compliance.
-
B.
procurement policy office
The procurement policy office is responsible for developing, implementing, and overseeing rules, guidelines, and standards that govern how an organization acquires goods and services to ensure fairness, compliance, and value for money.
-
C.
application management system
chosen
An application management system is a software platform that streamlines the end-to-end process of receiving, tracking, evaluating, and managing applications and related communications.
-
D.
Lisa application
The Lisa application is a software program designed to run on the Lisa operating environment, providing users with specific productivity or utility functions through a graphical user interface.
-
E.
Supply-side platform
A supply-side platform is a technology system that helps digital publishers manage, optimize, and automate the selling of their advertising inventory across multiple ad exchanges and demand sources.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:42 p.m.