Triple

T37704076
Position Surface form Disambiguated ID Type / Status
Subject Ti:sapphire laser E939151 entity
Predicate tunableWavelengthRange P45250 FINISHED
Object ~650–1100 nm 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: ~650–1100 nm | Statement: [Ti:sapphire laser, tunableWavelengthRange, ~650–1100 nm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tunableWavelengthRange
Context triple: [Ti:sapphire laser, tunableWavelengthRange, ~650–1100 nm]
  • A. supportsWavelengthRange chosen
    Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
  • B. approximateWavelengthRange
    Indicates the range of wavelengths that approximately characterizes or bounds the phenomenon, object, or interaction in question.
  • C. usedWavelengthRange
    Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
  • D. wavelengthRangeLowerBoundMicrometers
    Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
  • 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_69f76edb49dc8190b951dce9ce6ef789 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb084760c8190a1554985d3c3cb7a completed May 6, 2026, 9:20 p.m.
PD Predicate disambiguation batch_69fbadf3cb548190ba3b7514f76b790a completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:18 p.m.