Triple
T10846159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOS |
E256013
|
entity |
| Predicate | coversWavelengthRange |
P45250
|
FINISHED |
| Object | ultraviolet |
—
|
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: ultraviolet | Statement: [FOS, coversWavelengthRange, ultraviolet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversWavelengthRange Context triple: [FOS, coversWavelengthRange, ultraviolet]
-
A.
supportsWavelengthRange
chosen
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
-
B.
usedWavelengthRange
Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
-
C.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
-
D.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
E.
spectralCoverageEnd
Indicates the upper limit of the spectral range (e.g., wavelength, frequency, or energy) covered by an observation, dataset, or instrument.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.