Triple
T7640802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naharkatiya oil field |
E172998
|
entity |
| Predicate | onshoreOffshore |
P72209
|
FINISHED |
| Object | onshore |
—
|
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 | Statement: [Naharkatiya oil field, onshoreOffshore, onshore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onshoreOffshore Context triple: [Naharkatiya oil field, onshoreOffshore, onshore]
-
A.
onshoreOrOffshore
chosen
Indicates whether something is located or occurring on land (onshore) or at sea/away from land (offshore).
-
B.
offshoreUnit
Indicates that one entity is an offshore facility or installation associated with, located near, or operating in relation to another entity (such as a geographic area, project, or jurisdiction).
-
C.
offshoreFeature
Indicates that a geographic or structural feature is located in a marine or aquatic area away from the shoreline.
-
D.
isOffshoreVersionOf
Indicates that one entity is a version or counterpart of another that is located, registered, or operated in an offshore jurisdiction.
-
E.
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).
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facd9dec8190ab3af9cdde9992e6 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.