Triple
T38044782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew Dragon Resilience |
E949586
|
entity |
| Predicate | crewOnAx-1 |
P94498
|
FINISHED |
| Object | Michael López-Alegría |
—
|
NE NERFINISHED |
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: Michael López-Alegría | Statement: [Crew Dragon Resilience, crewOnAx-1, Michael López-Alegría]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewOnAx-1 Context triple: [Crew Dragon Resilience, crewOnAx-1, Michael López-Alegría]
-
A.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
B.
crewEVA
Indicates that a crew member performs or participates in an extravehicular activity (spacewalk) outside their spacecraft.
-
C.
crewMemberInOrbit
Indicates that a person is serving as a crew member aboard a spacecraft or station that is currently in orbit.
-
D.
crewEVAPlanned
Indicates that a spacewalk (extravehicular activity) involving crew members is scheduled or planned to occur.
-
E.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:20 p.m.