Triple
T16788735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 5 |
E408046
|
entity |
| Predicate | spectralBandsMultispectralScanner |
P123775
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Landsat 5, spectralBandsMultispectralScanner, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectralBandsMultispectralScanner Context triple: [Landsat 5, spectralBandsMultispectralScanner, 4]
-
A.
hasSpectralChannel
Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
-
B.
numberOfSpectralChannels
chosen
Indicates the relationship specifying how many distinct spectral channels are associated with an entity or measurement.
-
C.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
D.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
E.
spectralResolution
Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21c49788190b9a2ca2101604f64 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.