Triple

T16357610
Position Surface form Disambiguated ID Type / Status
Subject GRACES E397222 entity
Predicate spectralResolutionMode P7238 FINISHED
Object high-resolution mode 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-resolution mode | Statement: [GRACES, spectralResolutionMode, high-resolution mode]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spectralResolutionMode
Context triple: [GRACES, spectralResolutionMode, high-resolution mode]
  • A. spectralResolution chosen
    Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
  • B. 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.
  • C. hasSpectralChannel
    Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
  • D. samplingResolution
    Indicates the level of detail or granularity at which data is sampled or measurements are taken in a process or system.
  • E. sensorResolution
    Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
  • 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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2fad0b1948190a66ec7d2a310cc83 completed April 18, 2026, 3:30 a.m.
PD Predicate disambiguation batch_69e226f37ecc819082af58b29b4e39d1 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:07 a.m.