Triple
T33246638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groningen gas extraction area |
E851118
|
entity |
| Predicate | mainGasQuality |
P22265
|
FINISHED |
| Object | low-calorific 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: low-calorific gas | Statement: [Groningen gas extraction area, mainGasQuality, low-calorific gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGasQuality Context triple: [Groningen gas extraction area, mainGasQuality, low-calorific gas]
-
A.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
B.
isGasRich
Indicates that an entity possesses a relatively high abundance or concentration of gas compared to a defined reference or threshold.
-
C.
roleInGas
Indicates that an entity has a specific functional or contextual role within a gas-related process, system, or environment.
-
D.
gasContent
chosen
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
E.
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.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6daf4ae588190b8884f67b6bc616d |
completed | May 3, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69f6d82fef788190b9ad19a36c0312dc |
completed | May 3, 2026, 5:08 a.m. |
Created at: May 1, 2026, 1:31 a.m.