Triple
T5443179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceaneering International |
E122185
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | offshore services company |
C18212
|
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: offshore services company Context triple: [Oceaneering International, instanceOf, offshore services company]
-
A.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
B.
shipbuilding firm
A shipbuilding firm is a company that designs, constructs, and sometimes repairs ships and other marine vessels for commercial, military, or private use.
-
C.
computer services company
A computer services company is an organization that provides technical expertise, support, and solutions related to computer systems, software, networks, and IT infrastructure for individuals or other businesses.
-
D.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
-
E.
air-to-air refuelling service provider
An air-to-air refuelling service provider is an organization that operates tanker aircraft and associated support systems to deliver in-flight fuel to receiver aircraft, extending their range, endurance, and mission effectiveness.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.