Triple
T10787917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSM-103 |
E254494
|
entity |
| Predicate | heatShieldLocation |
P28293
|
FINISHED |
| Object | base of command module |
—
|
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: base of command module | Statement: [CSM-103, heatShieldLocation, base of command module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatShieldLocation Context triple: [CSM-103, heatShieldLocation, base of command module]
-
A.
heatShieldType
Indicates the specific kind or category of heat shield associated with an object or system.
-
B.
heatShieldIssue
Indicates that there is a problem, defect, or concern affecting an object's heat shield or thermal protection system.
-
C.
heatShieldThickness
Indicates the thickness of a protective heat shield used to guard an object from high temperatures or thermal loads.
-
D.
heatShieldDiameter
Indicates the diameter measurement of a heat shield in the context of a system or object.
-
E.
shieldPosition
chosen
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.