Triple

T17046021
Position Surface form Disambiguated ID Type / Status
Subject Landsat 7 E413569 entity
Predicate multispectralBandResolution P25684 FINISHED
Object 30 meters 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: 30 meters | Statement: [Landsat 7, multispectralBandResolution, 30 meters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: multispectralBandResolution
Context triple: [Landsat 7, multispectralBandResolution, 30 meters]
  • A. spectralResolution
    Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
  • B. hasSpatialResolution chosen
    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. sensorResolution
    Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
  • D. hasSpectralChannel
    Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
  • E. numberOfSpectralChannels
    Indicates the relationship specifying how many distinct spectral channels are associated with an entity or measurement.
  • 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_69d886cd18288190b006abab23f811b7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3da9d7e988190a5e3991c7123f9b0 completed April 18, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69e35d60a588819084f53ef9f8b2e7c0 completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:33 a.m.