Triple
T34183756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atikokan, Ontario |
E876896
|
entity |
| Predicate | generatingStationFuelType |
P119629
|
FINISHED |
| Object | biomass |
—
|
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: biomass | Statement: [Atikokan, Ontario, generatingStationFuelType, biomass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatingStationFuelType Context triple: [Atikokan, Ontario, generatingStationFuelType, biomass]
-
A.
powerPlantFuel
chosen
Indicates that a power plant uses a particular fuel type as its energy source.
-
B.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
C.
powerplantOutput
Indicates the amount of energy or power produced by a power plant over a given period or at a specific moment.
-
D.
fuelTypeProduced
Indicates the type of fuel that is generated or produced by a given source, process, or facility.
-
E.
generationUnits
Indicates a relationship where specific units or components are responsible for generating or producing something within a system or process.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710075ce48190ad41ebd08e640c1e |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.