Triple
T11692397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX Dragon program |
E277899
|
entity |
| Predicate | heatShieldMaterial |
P1272
|
FINISHED |
| Object | PICA-X |
E57907
|
NE 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: PICA-X | Statement: [SpaceX Dragon program, heatShieldMaterial, PICA-X]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PICA-X Context triple: [SpaceX Dragon program, heatShieldMaterial, PICA-X]
-
A.
PICA-X
chosen
PICA-X is a SpaceX-developed, advanced heat shield material designed to protect Dragon spacecraft during the intense heat of atmospheric reentry.
-
B.
PICA
PICA is the abbreviation for Picatinny Arsenal, a U.S. Army research and manufacturing facility specializing in armaments and munitions development.
-
C.
PIXL
PIXL is a highly sensitive X-ray fluorescence spectrometer on NASA's Perseverance rover used to analyze the elemental composition of Martian rocks and soil at microscopic scales.
-
D.
PIK
PIK is a leading German research institute focused on analyzing the causes and impacts of climate change and developing strategies for sustainable solutions.
-
E.
PIK
PIK is the three-letter IATA airport code for Glasgow Prestwick Airport in South Ayrshire, Scotland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef1461b2f0819091ef2a0627ffe5f5 |
completed | April 27, 2026, 7:46 a.m. |
Created at: April 8, 2026, 9:40 p.m.