Triple
T16081373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanbu Aramco Sinopec Refining Company |
E390117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial company in Saudi Arabia |
C35951
|
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: industrial company in Saudi Arabia Context triple: [Yanbu Aramco Sinopec Refining Company, instanceOf, industrial company in Saudi Arabia]
-
A.
Saudi Arabian company
A Saudi Arabian company is a business entity established and operating under the laws and regulations of the Kingdom of Saudi Arabia, typically engaged in commercial, industrial, or service activities within domestic and international markets.
-
B.
Kuwaiti company
A Kuwaiti company is a business entity established and operating under the laws and regulations of the State of Kuwait, typically engaged in commercial, industrial, or service activities within local and international markets.
-
C.
refining company
chosen
A refining company is a business entity that processes raw materials, such as crude oil or metals, into more valuable, usable products through industrial refining operations.
-
D.
manufacturing company
A manufacturing company is an organization that transforms raw materials or components into finished goods through industrial processes, machinery, and labor for sale to other businesses or consumers.
-
E.
industrial holding company
An industrial holding company is a parent corporation that owns controlling interests in multiple industrial or manufacturing businesses, managing them strategically while typically leaving day-to-day operations to subsidiary management.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.