Triple
T20948468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-38 Crew Return Vehicle prototype |
E515912
|
entity |
| Predicate | crewSurvivalSystem |
P64179
|
FINISHED |
| Object | pressurized cabin |
—
|
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: pressurized cabin | Statement: [X-38 Crew Return Vehicle prototype, crewSurvivalSystem, pressurized cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewSurvivalSystem Context triple: [X-38 Crew Return Vehicle prototype, crewSurvivalSystem, pressurized cabin]
-
A.
crewLifeSupportCapability
chosen
Indicates the ability of a system or vehicle to provide and maintain necessary life support functions for its crew.
-
B.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
C.
survivesExpedition
Indicates that an entity endures and remains alive through the duration of a specified expedition or journey.
-
D.
survivalTheme
Indicates that the relationship or situation centers on the struggle to stay alive or endure extreme hardship.
-
E.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fadab7708190bb3a10bdd3f32d90 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1 p.m.