Triple

T11119721
Position Surface form Disambiguated ID Type / Status
Subject Lyman Alpha Photometer E262983 entity
Predicate wavelengthRegion P7244 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: [Lyman Alpha Photometer, wavelengthRegion, ultraviolet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wavelengthRegion
Context triple: [Lyman Alpha Photometer, wavelengthRegion, ultraviolet]
  • A. spectralRegion chosen
    Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
  • 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. supportsWavelengthRange
    Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
  • E. channelWavelength
    Indicates the specific wavelength at which a given channel operates or is defined.
  • 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79af7b72c8190a19dbcbb3a69fb5b completed April 9, 2026, 12:26 p.m.
PD Predicate disambiguation batch_69d7441efe948190ae4ab020121e169d completed April 9, 2026, 6:15 a.m.
Created at: April 8, 2026, 9:28 p.m.