Triple
T11692908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA PICA |
E277912
|
entity |
| Predicate | heatShieldForm |
P14978
|
FINISHED |
| Object | monolithic forebody heat shield 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: monolithic forebody heat shield tiles | Statement: [NASA PICA, heatShieldForm, monolithic forebody heat shield tiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatShieldForm Context triple: [NASA PICA, heatShieldForm, monolithic forebody heat shield tiles]
-
A.
heatShieldFunction
Indicates that an entity serves to protect another entity or system from excessive heat or thermal damage.
-
B.
heatShieldType
chosen
Indicates the specific kind or category of heat shield associated with an object or system.
-
C.
heatShieldIssue
Indicates that there is a problem, defect, or concern affecting an object's heat shield or thermal protection system.
-
D.
heatShieldThickness
Indicates the thickness of a protective heat shield used to guard an object from high temperatures or thermal loads.
-
E.
heatShieldDiameter
Indicates the diameter measurement of a heat shield in the context of a system or object.
- 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_69d8a47b9eb48190976a35e91e25b56b |
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.