Triple
T868993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury |
E18768
|
entity |
| Predicate | minSurfaceTemperature |
P20352
|
FINISHED |
| Object | 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: about −180 degrees Celsius | Statement: [Mercury, minSurfaceTemperature, about −180 degrees Celsius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minSurfaceTemperature Context triple: [Mercury, minSurfaceTemperature, about −180 degrees Celsius]
-
A.
surfaceTemperatureRange
Indicates the range between the minimum and maximum surface temperatures observed or allowed for an entity.
-
B.
hasAverageSurfaceTemperature
Indicates that an entity is associated with a specific mean value of its surface temperature over a defined period or condition.
-
C.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
E.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.