Triple
T5182613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle iSupplier Portal |
E116956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | web-based procurement application |
C17763
|
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-based procurement application Context triple: [Oracle iSupplier Portal, instanceOf, web-based 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.
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.
-
D.
e-commerce platform
An e-commerce platform is a digital system that enables businesses and consumers to browse, purchase, and manage the sale of goods and services online, including product listings, payments, and order fulfillment.
-
E.
government procurement agreement
A government procurement agreement is a formal arrangement that sets rules and commitments for how public authorities purchase goods, services, and works, typically to ensure transparency, fairness, and non-discrimination among suppliers.
- F. None of above. chosen
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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:46 p.m.