Triple
T26530113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS radiometer |
E670795
|
entity |
| Predicate | hasSpectralRegion |
P7244
|
FINISHED |
| Object | thermal infrared |
—
|
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: thermal infrared | Statement: [MAS radiometer, hasSpectralRegion, thermal infrared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectralRegion Context triple: [MAS radiometer, hasSpectralRegion, thermal infrared]
-
A.
spectralRegion
chosen
Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
-
B.
hasSpectralChannel
Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
-
C.
spectrumContains
Indicates that a given spectrum includes or exhibits a specified component, feature, or range within it.
-
D.
hasSpectrumRole
Indicates that an entity holds a specific role, function, or responsibility within a defined spectrum-related context or framework.
-
E.
hasSpectralLines
Indicates that one entity exhibits or is characterized by specific spectral lines associated with another entity.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 1:35 a.m.