Triple
T8378882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross-track Infrared Sounder |
E197639
|
entity |
| Predicate | spectrometerType |
P82398
|
FINISHED |
| Object | Fourier transform spectrometer |
—
|
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: Fourier transform spectrometer | Statement: [Cross-track Infrared Sounder, spectrometerType, Fourier transform spectrometer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectrometerType Context triple: [Cross-track Infrared Sounder, spectrometerType, Fourier transform spectrometer]
-
A.
spectrographType
Indicates the specific kind or category of spectrograph associated with an instrument or observation.
-
B.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
C.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
-
D.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
E.
spectralResolution
Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c3dc1881908081c6a2829deb5a |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.