Triple
T9867148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-27 |
E239860
|
entity |
| Predicate | heatShieldIssue |
P90958
|
FINISHED |
| Object | loss and damage of many thermal protection tiles |
—
|
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: loss and damage of many thermal protection tiles | Statement: [STS-27, heatShieldIssue, loss and damage of many thermal protection tiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatShieldIssue Context triple: [STS-27, heatShieldIssue, loss and damage of many thermal protection tiles]
-
A.
heatShieldType
Indicates the specific kind or category of heat shield associated with an object or system.
-
B.
heatShieldThickness
Indicates the thickness of a protective heat shield used to guard an object from high temperatures or thermal loads.
-
C.
heatShieldDiameter
Indicates the diameter measurement of a heat shield in the context of a system or object.
-
D.
heatSource
Indicates that one entity serves as a source of heat or heating for another entity.
-
E.
thermalControl
Indicates a relationship where one entity regulates, adjusts, or maintains the temperature or thermal conditions of another entity or environment.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d209ac8190b9bc9ff017a132da |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:36 p.m.