Triple
T8880461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Kivu |
E211397
|
entity |
| Predicate | hasDissolvedMethaneReserves |
P68772
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Kivu, hasDissolvedMethaneReserves, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDissolvedMethaneReserves Context triple: [Lake Kivu, hasDissolvedMethaneReserves, true]
-
A.
isGasRich
chosen
Indicates that an entity possesses a relatively high abundance or concentration of gas compared to a defined reference or threshold.
-
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.
hasPersistentGasEmissions
Indicates that an entity continuously or repeatedly releases gaseous substances over an extended period.
-
D.
hasCoalBasin
Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
-
E.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61677c9c8190aa09dc2a05d4cf95 |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.