Triple
T11120472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Valley region |
E263000
|
entity |
| Predicate | energyResourceCategory |
P89594
|
FINISHED |
| Object | fossil fuels |
—
|
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: fossil fuels | Statement: [South Valley region, energyResourceCategory, fossil fuels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyResourceCategory Context triple: [South Valley region, energyResourceCategory, fossil fuels]
-
A.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
B.
energyAspect
Indicates a relationship where one entity represents an aspect, component, or characteristic related to the energy properties or behavior of another entity.
-
C.
energy
Indicates that an entity possesses, produces, consumes, or is associated with a quantifiable amount or type of energy.
-
D.
hasEnergyResource
chosen
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
E.
energyThroughputCategory
Indicates the classification of an entity based on the amount or level of energy it processes or transfers over a given period.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af911b881908168f23a4918231c |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.