Triple
T28323265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxony-Leipzig lignite mining area |
E717334
|
entity |
| Predicate | energyResourceType |
P5332
|
FINISHED |
| Object | fossil fuel |
—
|
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 fuel | Statement: [Saxony-Leipzig lignite mining area, energyResourceType, fossil fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyResourceType Context triple: [Saxony-Leipzig lignite mining area, energyResourceType, fossil fuel]
-
A.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
B.
energyName
Indicates that a specific name or label is assigned to an energy-related quantity, type, or resource.
-
C.
powerPlantFuel
Indicates that a power plant uses a particular fuel type as its energy source.
-
D.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
E.
energySourceDepiction
Indicates that one entity is a visual or symbolic representation of the energy source associated with another entity.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 12:26 a.m.