Triple
T21369831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuangyashan |
E527023
|
entity |
| Predicate | hasPrimaryEnergyResource |
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: [Shuangyashan, hasPrimaryEnergyResource, fossil fuels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEnergyResource Context triple: [Shuangyashan, hasPrimaryEnergyResource, fossil fuels]
-
A.
hasEnergyResource
chosen
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
B.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
C.
hasRenewableEnergyPotential
Indicates that an entity possesses conditions or characteristics that make it suitable for generating energy from renewable sources.
-
D.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
E.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0adbbc081908ed4d839f7cf8f38 |
completed | April 22, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:10 p.m.