Triple

T15516823
Position Surface form Disambiguated ID Type / Status
Subject Fiber-fed Extended Range Optical Spectrograph E368854 entity
Predicate hasSpectralResolution P7238 FINISHED
Object high 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 | Statement: [Fiber-fed Extended Range Optical Spectrograph, hasSpectralResolution, high]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpectralResolution
Context triple: [Fiber-fed Extended Range Optical Spectrograph, hasSpectralResolution, high]
  • A. spectralResolution chosen
    Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
  • B. hasSpectralChannel
    Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
  • C. hasSpectrograph
    Indicates that one entity is equipped with or contains a spectrograph instrument.
  • D. hasSpatialResolution
    Indicates that something is characterized by a specific level of spatial detail or granularity at which it can represent or distinguish features in space.
  • E. hasSpectralLines
    Indicates that one entity exhibits or is characterized by specific spectral lines associated with another entity.
  • 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_69d85a1794cc8190b0b428716296e63e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e04033303c8190a87b6384f68a6921 completed April 16, 2026, 1:49 a.m.
PD Predicate disambiguation batch_69ded2896a9c8190a8b9627deb3c17b4 completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 4:02 a.m.