Triple
T23169020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Nova FPSO |
E578791
|
entity |
| Predicate | subseaTieBack |
P151193
|
FINISHED |
| Object | Terra Nova subsea wells |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Terra Nova subsea wells | Statement: [Terra Nova FPSO, subseaTieBack, Terra Nova subsea wells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subseaTieBack Context triple: [Terra Nova FPSO, subseaTieBack, Terra Nova subsea wells]
-
A.
subseaSection
Indicates a relationship where one section is located beneath the sea, typically as a distinct underwater part of a larger structure, route, or system.
-
B.
hasRegionalSubsea
Indicates that one entity includes or is associated with another entity that operates or exists within a specific regional subsea (undersea) area.
-
C.
isSubseaBasinOf
Indicates that a geological basin is located beneath the sea and is part of, or contained within, a larger marine or oceanic region.
-
D.
hasSubseaTunnel
Indicates that one location or structure is connected to another by an underwater tunnel.
-
E.
lengthUnderseaSection
Indicates that the specified length pertains to the portion of an object or route that lies beneath the sea surface.
- F. None of above. chosen
Provenance (4 batches)
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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2e5e208190839ec37de4b974af |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:03 p.m.