Triple
T7722614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle thermal protection system |
E175049
|
entity |
| Predicate | maxDesignTemperature |
P20351
|
FINISHED |
| Object | approximately 1650 °C |
—
|
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: approximately 1650 °C | Statement: [Space Shuttle thermal protection system, maxDesignTemperature, approximately 1650 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxDesignTemperature Context triple: [Space Shuttle thermal protection system, maxDesignTemperature, approximately 1650 °C]
-
A.
maxSurfaceTemperature
chosen
Indicates the highest temperature that the surface of an entity can reach or sustain under specified conditions.
-
B.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
hasMinTemperature
Indicates that something possesses or is associated with a specified minimum temperature value.
-
E.
minSurfaceTemperature
Indicates the lowest temperature value observed or allowed on the surface of an object or environment.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.