Triple
T28711184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microwave Sounding Unit |
E729834
|
entity |
| Predicate | primaryVariable |
P202258
|
FINISHED |
| Object | atmospheric temperature |
—
|
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: atmospheric temperature | Statement: [Microwave Sounding Unit, primaryVariable, atmospheric temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVariable Context triple: [Microwave Sounding Unit, primaryVariable, atmospheric temperature]
-
A.
primaryValue
Indicates the main or most significant value associated with an entity, attribute, or measurement within a given context.
-
B.
primaryVariant
Indicates that one entity is the main or canonical version among multiple related variants of another entity.
-
C.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
E.
primaryField
Indicates the main area of focus, discipline, or domain most centrally associated with an entity.
- F. None of above. chosen
Provenance (4 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_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_6a00694e9e008190b7c941d2f7527dff |
completed | May 10, 2026, 11:17 a.m. |
Created at: April 28, 2026, 5:48 a.m.