Triple
T35561141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE |
E1027637
|
entity |
| Predicate | bandWavelengths |
P92640
|
FINISHED |
| Object | 3.4 μm |
—
|
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: 3.4 μm | Statement: [WISE, bandWavelengths, 3.4 μm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandWavelengths Context triple: [WISE, bandWavelengths, 3.4 μm]
-
A.
supportsWavelengthRange
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
-
B.
approximateWavelengthRange
Indicates the range of wavelengths that approximately characterizes or bounds the phenomenon, object, or interaction in question.
-
C.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
-
D.
channelWavelength
chosen
Indicates the specific wavelength at which a given channel operates or is defined.
-
E.
usedWavelengthRange
Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.