Triple

T37574169
Position Surface form Disambiguated ID Type / Status
Subject Licancabur crater lake E934770 entity
Predicate UVIndexCharacteristic P81429 FINISHED
Object very high UV index 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: very high UV index | Statement: [Licancabur crater lake, UVIndexCharacteristic, very high UV index]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UVIndexCharacteristic
Context triple: [Licancabur crater lake, UVIndexCharacteristic, very high UV index]
  • A. hasSolarRadiation chosen
    Indicates that an entity is subject to, receives, or is characterized by a certain amount or presence of solar radiation.
  • B. absorbsUVLightAt
    Indicates that one entity takes in or attenuates ultraviolet light at a specified wavelength, range, or condition associated with another entity.
  • 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. sunRayType
    Indicates the specific kind or classification of sun ray associated with or emitted by an entity.
  • E. sunshineHoursPerYear
    Indicates the total number of hours in a year during which a location receives direct sunshine.
  • 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_69f76ecd99148190be327e391a70f5b6 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba61dff5081909fec88a7aeb0c8a1 completed May 6, 2026, 8:35 p.m.
PD Predicate disambiguation batch_69fba350e9a8819095893229d9643572 completed May 6, 2026, 8:23 p.m.
Created at: May 3, 2026, 4:17 p.m.