Triple
T16973563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 6 |
E411748
|
entity |
| Predicate | spectralInstrumentType |
P125445
|
FINISHED |
| Object | multispectral scanner |
—
|
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: multispectral scanner | Statement: [Landsat 6, spectralInstrumentType, multispectral scanner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectralInstrumentType Context triple: [Landsat 6, spectralInstrumentType, multispectral scanner]
-
A.
spectrometerType
Indicates the specific kind or category of spectrometer associated with or used in relation to an entity.
-
B.
spectrographType
Indicates the specific kind or category of spectrograph associated with an instrument or observation.
-
C.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
D.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
E.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0af06688190a77682aa297cd27e |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:31 a.m.