Triple
T27335676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kipnuk, Alaska |
E689937
|
entity |
| Predicate | hasPrimaryEnergyUse |
P160998
|
FINISHED |
| Object | fuel oil for heating |
—
|
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: fuel oil for heating | Statement: [Kipnuk, Alaska, hasPrimaryEnergyUse, fuel oil for heating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEnergyUse Context triple: [Kipnuk, Alaska, hasPrimaryEnergyUse, fuel oil for heating]
-
A.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
B.
electricityUse
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
C.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
-
D.
energyStandard
Indicates that an entity complies with, is classified by, or is governed according to a specified energy-related standard or efficiency criterion.
-
E.
usesEnergy
chosen
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 27, 2026, 11:40 a.m.