Triple
T20814186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed Martin X-33 |
E512390
|
entity |
| Predicate | thermalProtectionSystemType |
P14978
|
FINISHED |
| Object | metallic shingles |
—
|
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: metallic shingles | Statement: [Lockheed Martin X-33, thermalProtectionSystemType, metallic shingles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalProtectionSystemType Context triple: [Lockheed Martin X-33, thermalProtectionSystemType, metallic shingles]
-
A.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
B.
heatShieldType
chosen
Indicates the specific kind or category of heat shield associated with an object or system.
-
C.
hasIntruderDetectionSystem
Indicates that an entity is equipped with a system designed to detect unauthorized or intruding entities.
-
D.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
E.
hasThermalCharacteristic
Indicates that an entity possesses a specific thermal property or behavior, such as conductivity, capacity, or response to temperature.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d4e43c8190aecce82a3f7e2de0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.