Triple
T35565129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnedah Basin |
E1027748
|
entity |
| Predicate | hasHydrocarbonPotential |
P43884
|
FINISHED |
| Object | gas |
—
|
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: gas | Statement: [Gunnedah Basin, hasHydrocarbonPotential, gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydrocarbonPotential Context triple: [Gunnedah Basin, hasHydrocarbonPotential, gas]
-
A.
hydrocarbonPotential
chosen
Indicates the degree to which a geological unit or material is capable of generating, containing, or yielding hydrocarbons such as oil or natural gas.
-
B.
hasHydrocarbonTraps
Indicates the presence of geological structures or conditions that can accumulate and retain hydrocarbons such as oil or gas.
-
C.
discoveredHydrocarbons
Indicates that an entity has found or identified the presence of hydrocarbons in or associated with another entity or location.
-
D.
hydrocarbonMaturity
Indicates the degree to which organic matter in a rock has been thermally transformed into hydrocarbons capable of generation and expulsion.
-
E.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.