Triple
T476171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Webb Space Telescope |
E9066
|
entity |
| Predicate | designedOperatingTemperature |
P3958
|
FINISHED |
| Object | around 40 Kelvin |
—
|
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: around 40 Kelvin | Statement: [James Webb Space Telescope, designedOperatingTemperature, around 40 Kelvin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedOperatingTemperature Context triple: [James Webb Space Telescope, designedOperatingTemperature, around 40 Kelvin]
-
A.
operatingTemperature
chosen
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
B.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
C.
surfaceTemperatureRange
Indicates the range between the minimum and maximum surface temperatures observed or allowed for an entity.
-
D.
temperatureControlMethod
Indicates the method or mechanism used to regulate or maintain a desired temperature.
-
E.
coreTemperature
Indicates that an entity has a specific internal or central temperature value.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03b5e5081908ee3dba9d19a6871 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.