Triple
T6125374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-band |
E136582
|
entity |
| Predicate | wavelengthRangeUpper |
P42117
|
FINISHED |
| Object | 15 cm |
—
|
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: 15 cm | Statement: [S-band, wavelengthRangeUpper, 15 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wavelengthRangeUpper Context triple: [S-band, wavelengthRangeUpper, 15 cm]
-
A.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
-
B.
spectralCoverageEnd
chosen
Indicates the upper limit of the spectral range (e.g., wavelength, frequency, or energy) covered by an observation, dataset, or instrument.
-
C.
supportsWavelengthRange
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
-
D.
upperBandWidth
Indicates the maximum bandwidth limit or upper threshold of data transfer capacity allowed or supported in a given context.
-
E.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c2791948190ba33458edfd1ebe8 |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.