Triple
T15744149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyman series in hydrogen spectrum |
E381675
|
entity |
| Predicate | LymanDeltaWavelengthApproximate |
P120458
|
FINISHED |
| Object | 95.0 nm |
—
|
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: 95.0 nm | Statement: [Lyman series in hydrogen spectrum, LymanDeltaWavelengthApproximate, 95.0 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LymanDeltaWavelengthApproximate Context triple: [Lyman series in hydrogen spectrum, LymanDeltaWavelengthApproximate, 95.0 nm]
-
A.
wavelengthApproximate
Indicates that one entity’s wavelength is approximately equal to, or closely matches, the wavelength of another entity.
-
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.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
D.
pumpingWavelength
Indicates the wavelength at which energy is supplied to excite a system or medium in a pumping process.
-
E.
channelWavelength
Indicates the specific wavelength at which a given channel operates or is defined.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:46 a.m.