Triple
T8520728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAS-2 |
E201686
|
entity |
| Predicate | wavelengthRangeObserved |
P38137
|
FINISHED |
| Object | gamma rays |
—
|
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: gamma rays | Statement: [SAS-2, wavelengthRangeObserved, gamma rays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wavelengthRangeObserved Context triple: [SAS-2, wavelengthRangeObserved, gamma rays]
-
A.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
B.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
-
C.
supportsWavelengthRange
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
-
D.
observingBand
chosen
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
E.
wavelengthDependence
Indicates that one quantity or effect varies as a function of the wavelength of radiation or a wave.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.