Triple
T16496551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Microwave Scanning Radiometer for EOS |
E400697
|
entity |
| Predicate | scanAngle |
P88621
|
FINISHED |
| Object | 55 degrees |
—
|
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: 55 degrees | Statement: [Advanced Microwave Scanning Radiometer for EOS, scanAngle, 55 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanAngle Context triple: [Advanced Microwave Scanning Radiometer for EOS, scanAngle, 55 degrees]
-
A.
projectionAngle
Indicates the angle at which one entity is projected onto or relative to another reference (such as a line, plane, or direction).
-
B.
hasViewingAngles
chosen
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
C.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
D.
maxVerticalAngle
Indicates the greatest vertical angular difference or tilt between two entities or directions.
-
E.
angleOfIncident
Indicates the angle at which one entity (such as a ray, line, or object) strikes or approaches the surface or boundary of 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e343a7c81909e04cbaaa40e2531 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.