Triple
T33525416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cymric Oil Field |
E858624
|
entity |
| Predicate | isOnshoreOffshore |
P72209
|
FINISHED |
| Object | onshore field |
—
|
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: onshore field | Statement: [Cymric Oil Field, isOnshoreOffshore, onshore field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnshoreOffshore Context triple: [Cymric Oil Field, isOnshoreOffshore, onshore field]
-
A.
onshoreOrOffshore
chosen
Indicates whether something is located or occurring on land (onshore) or at sea/away from land (offshore).
-
B.
isOffshoreVersionOf
Indicates that one entity is a version or counterpart of another that is located, registered, or operated in an offshore jurisdiction.
-
C.
locatedOffshoreOf
Indicates that one entity is situated in an offshore area (typically at sea) relative to another, such as off the coast or maritime boundary of that reference entity.
-
D.
hasOffshoreLegs
Indicates that an entity has one or more operational components, activities, or segments located offshore (e.g., at sea or outside its home jurisdiction).
-
E.
isOffshoreAirport
Indicates that an airport is located offshore, such as on an artificial island or platform away from the mainland.
- F. None of above.
Provenance (3 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.