Triple
T30619485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shedgum |
E779406
|
entity |
| Predicate | hydrocarbonBasin |
P36894
|
FINISHED |
| Object | Arabian Basin |
—
|
NE NERFINISHED |
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: Arabian Basin | Statement: [Shedgum, hydrocarbonBasin, Arabian Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydrocarbonBasin Context triple: [Shedgum, hydrocarbonBasin, Arabian Basin]
-
A.
isSubseaBasinOf
Indicates that a geological basin is located beneath the sea and is part of, or contained within, a larger marine or oceanic region.
-
B.
hydrocarbonPotential
Indicates the degree to which a geological unit or material is capable of generating, containing, or yielding hydrocarbons such as oil or natural gas.
-
C.
basinPartOf
chosen
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
D.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
E.
hasHydrocarbonTraps
Indicates the presence of geological structures or conditions that can accumulate and retain hydrocarbons such as oil or gas.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:26 p.m.