Triple
T17245741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Space Simulator |
E418619
|
entity |
| Predicate | canReachTemperature |
P3958
|
FINISHED |
| Object | down to about -180 degrees Celsius |
—
|
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: down to about -180 degrees Celsius | Statement: [Large Space Simulator, canReachTemperature, down to about -180 degrees Celsius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReachTemperature Context triple: [Large Space Simulator, canReachTemperature, down to about -180 degrees Celsius]
-
A.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
operatingTemperature
chosen
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
C.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
D.
hasPlatformHeaters
Indicates that a platform is equipped with heaters to provide warmth or prevent ice and snow accumulation.
-
E.
temperatureControlMethod
Indicates the method or mechanism used to regulate or maintain a desired temperature.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.