Triple
T21123521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 8 |
E520491
|
entity |
| Predicate | spectralBandsTIRS |
P123770
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Landsat 8, spectralBandsTIRS, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectralBandsTIRS Context triple: [Landsat 8, spectralBandsTIRS, 2]
-
A.
numberOfSpectralChannels
Indicates the relationship specifying how many distinct spectral channels are associated with an entity or measurement.
-
B.
hasSpectralChannel
Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
-
C.
numberOfInfraredChannels
chosen
Indicates the count of distinct infrared channels associated with or supported by an entity.
-
D.
spectralRegion
Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
-
E.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72236b2d88190bef9f0cd6924ca92 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.