Triple
T147133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magellan Echellette Spectrograph |
E3354
|
entity |
| Predicate | wavelengthCoverage |
P4679
|
FINISHED |
| Object | ~3100 Å to ~1 micron |
—
|
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: ~3100 Å to ~1 micron | Statement: [Magellan Echellette Spectrograph, wavelengthCoverage, ~3100 Å to ~1 micron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wavelengthCoverage Context triple: [Magellan Echellette Spectrograph, wavelengthCoverage, ~3100 Å to ~1 micron]
-
A.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
hasLandCoverage
Indicates that a specified area or region is covered or occupied by a particular type of land surface or land use.
-
C.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
D.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
E.
range
chosen
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.