Triple
T21135003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HL-20 Personnel Launch System |
E520793
|
entity |
| Predicate | crewEnvironment |
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: [HL-20 Personnel Launch System, crewEnvironment, pressurized cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewEnvironment Context triple: [HL-20 Personnel Launch System, crewEnvironment, pressurized cabin]
-
A.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
B.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
C.
crewMate
Indicates that two entities are members of the same crew or team, sharing a common group affiliation or working together in a joint capacity.
-
D.
crewLifeSupportCapability
chosen
Indicates the ability of a system or vehicle to provide and maintain necessary life support functions for its crew.
-
E.
crewEVA
Indicates that a crew member performs or participates in an extravehicular activity (spacewalk) outside their spacecraft.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723592fd48190ba5977a1b229d51e |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.