Triple
T28379603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock John Fort |
E718854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | offshore structure |
C16149
|
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 structure Context triple: [Knock John Fort, instanceOf, offshore structure]
-
A.
maritime structure
chosen
A maritime structure is a man-made construction located in or near bodies of water, designed to support marine activities such as navigation, transportation, resource extraction, or coastal protection.
-
B.
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.
-
C.
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.
-
D.
offshore oil and gas development project
An offshore oil and gas development project is a large-scale, capital-intensive initiative that plans, designs, constructs, and operates facilities at sea to extract, process, and transport hydrocarbons from subsea reservoirs to market.
-
E.
deepwater fabrication facility
A deepwater fabrication facility is a specialized industrial site where large offshore structures and subsea components are engineered, assembled, and integrated for deployment in deepwater oil, gas, or renewable energy projects.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:05 a.m.