Triple
T37704104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ti:sapphire laser |
E939151
|
entity |
| Predicate | typicalPumpWavelength |
P103090
|
FINISHED |
| Object | ~532 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: ~532 nm | Statement: [Ti:sapphire laser, typicalPumpWavelength, ~532 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPumpWavelength Context triple: [Ti:sapphire laser, typicalPumpWavelength, ~532 nm]
-
A.
pumpingWavelength
chosen
Indicates the wavelength at which energy is supplied to excite a system or medium in a pumping process.
-
B.
emitsWavelength
Indicates that one entity produces or gives off electromagnetic radiation at a specified wavelength associated with another entity.
-
C.
focusWavelength
Indicates the specific wavelength at which an optical system or device is adjusted to achieve optimal focus.
-
D.
wavelengthOfReadingLaser
Indicates the specific wavelength at which the reading laser operates during a reading or scanning process.
-
E.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.