Triple
T13066021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upington |
E329324
|
entity |
| Predicate | solarResource |
P81429
|
FINISHED |
| Object | high solar radiation levels |
—
|
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: high solar radiation levels | Statement: [Upington, solarResource, high solar radiation levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solarResource Context triple: [Upington, solarResource, high solar radiation levels]
-
A.
isSolar
Indicates that something is powered by, related to, or derived from the sun or solar energy.
-
B.
solarArray
Indicates that one entity functions as a solar array for another, typically providing solar-generated electrical power or energy.
-
C.
hasMaximumSolarInsolation
Indicates that an entity receives the highest level of solar radiation or sunlight intensity compared to relevant alternatives or within a given context.
-
D.
hasSolarRadiation
chosen
Indicates that an entity is subject to, receives, or is characterized by a certain amount or presence of solar radiation.
-
E.
hasMinimumSolarInsolation
Indicates that an entity receives at least a specified minimum amount of solar energy (insolation) over a given area and time 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980eb81948190b27eb9ae19978079 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 8:59 p.m.