Triple
T12080524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | erbium-doped fiber amplifier |
E287664
|
entity |
| Predicate | pumpingWavelength |
P103090
|
FINISHED |
| Object | 980 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: 980 nm | Statement: [erbium-doped fiber amplifier, pumpingWavelength, 980 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pumpingWavelength Context triple: [erbium-doped fiber amplifier, pumpingWavelength, 980 nm]
-
A.
channelWavelength
Indicates the specific wavelength at which a given channel operates or is defined.
-
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.
primaryWavelength
Indicates the main or dominant wavelength associated with an entity, such as the principal wavelength at which it emits, reflects, or operates.
-
D.
usedWavelengthRange
Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
-
E.
wavelengthDependence
Indicates that one quantity or effect varies as a function of the wavelength of radiation or a wave.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:48 p.m.