Triple
T7722613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle thermal protection system |
E175049
|
entity |
| Predicate | reusable |
P5431
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Space Shuttle thermal protection system, reusable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reusable Context triple: [Space Shuttle thermal protection system, reusable, true]
-
A.
reusability
chosen
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
B.
designedForReusability
Indicates that something has been intentionally created or configured so it can be used multiple times without needing to be discarded or fundamentally rebuilt.
-
C.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
D.
reusabilityImpact
Indicates how the ability to reuse something (such as a component, resource, or design) affects outcomes, performance, or other relevant factors in a given context.
-
E.
rechargeable
Indicates that an entity can have its stored energy replenished, typically by being connected to a power source, and thus can be used repeatedly rather than discarded after a single use.
- 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.