Triple
T37633730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manus Regional Processing Centre |
E936423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | offshore processing centre |
C65058
|
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 processing centre Context triple: [Manus Regional Processing Centre, instanceOf, offshore processing centre]
-
A.
offshore petroleum export facility
An offshore petroleum export facility is a marine-based installation that receives, stores, and transfers produced oil or gas from offshore fields to tankers or pipelines for transport to onshore markets.
-
B.
offshore services company
An offshore services company is a business entity that provides specialized professional, financial, or operational services from a foreign jurisdiction, often to leverage regulatory, tax, or cost advantages for its clients.
-
C.
operations and maintenance center
An operations and maintenance center is a centralized facility responsible for monitoring, managing, and servicing systems, equipment, or infrastructure to ensure their reliable and efficient ongoing performance.
-
D.
offshore airport
An offshore airport is an aviation facility constructed on platforms or artificial islands located at sea, designed to handle air traffic while minimizing noise and land-use impacts on coastal or urban areas.
-
E.
floating production storage and offloading vessel
A floating production storage and offloading vessel is an offshore ship-shaped facility that processes hydrocarbons from subsea wells, stores the produced oil, and offloads it to shuttle tankers for transport.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.