Triple
T28711198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microwave Sounding Unit |
E729834
|
entity |
| Predicate | dataProcessedInto |
P60098
|
FINISHED |
| Object | temperature profile products |
—
|
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: temperature profile products | Statement: [Microwave Sounding Unit, dataProcessedInto, temperature profile products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProcessedInto Context triple: [Microwave Sounding Unit, dataProcessedInto, temperature profile products]
-
A.
dataProcessedAt
Indicates the time or location at which the data was processed.
-
B.
processedTo
chosen
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
C.
dataProcessingStyle
Indicates the manner, method, or approach by which data is processed or handled in a given context.
-
D.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
E.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:48 a.m.