Triple
T14986593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aliso Canyon Oil Field |
E373717
|
entity |
| Predicate | gasTypeStored |
P22265
|
FINISHED |
| Object | methane-dominant natural 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: methane-dominant natural gas | Statement: [Aliso Canyon Oil Field, gasTypeStored, methane-dominant natural gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasTypeStored Context triple: [Aliso Canyon Oil Field, gasTypeStored, methane-dominant natural gas]
-
A.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
B.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
C.
gasContent
chosen
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
D.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
E.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7007588819095bb1de029a6f2eb |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.