Triple
T11692885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA PICA |
E277912
|
entity |
| Predicate | thermalProtectionMechanism |
P15826
|
FINISHED |
| Object | ablation |
—
|
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: ablation | Statement: [NASA PICA, thermalProtectionMechanism, ablation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalProtectionMechanism Context triple: [NASA PICA, thermalProtectionMechanism, ablation]
-
A.
thermalControl
Indicates a relationship where one entity regulates, adjusts, or maintains the temperature or thermal conditions of another entity or environment.
-
B.
coreProtection
Indicates that an entity provides essential safeguarding or defense for another entity’s central or most critical component.
-
C.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
D.
hasThermalActivity
Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
-
E.
protectionType
chosen
Indicates the kind or method of protection that is applied to or associated with an entity.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47a3ddc819098e208611148d15b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.