Triple
T16756598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Services Corporation SAOG |
E407222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Omani company |
C37981
|
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: Omani company Context triple: [Port Services Corporation SAOG, instanceOf, Omani company]
-
A.
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.
-
B.
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.
-
C.
Omani government body
An Omani government body is an official public-sector organization in the Sultanate of Oman responsible for implementing national policies, delivering public services, and regulating specific domains in accordance with Omani law and state objectives.
-
D.
Malaysian company
A Malaysian company is a legally registered business entity operating in Malaysia, governed by local corporate laws and regulations, and engaged in commercial, industrial, or professional activities.
-
E.
company based in Morocco
A company based in Morocco is an organization legally registered and operating within Moroccan jurisdiction, conducting commercial, industrial, or service activities in accordance with local laws and regulations.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.