Triple
T38044771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew Dragon Resilience |
E949586
|
entity |
| Predicate | crewOnInspiration4 |
P94498
|
FINISHED |
| Object | Jared Isaacman |
—
|
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: Jared Isaacman | Statement: [Crew Dragon Resilience, crewOnInspiration4, Jared Isaacman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewOnInspiration4 Context triple: [Crew Dragon Resilience, crewOnInspiration4, Jared Isaacman]
-
A.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
B.
crewEVAPlanned
Indicates that a spacewalk (extravehicular activity) involving crew members is scheduled or planned to occur.
-
C.
crewEVA
Indicates that a crew member performs or participates in an extravehicular activity (spacewalk) outside their spacecraft.
-
D.
providedCrewForMissionType
Indicates that an entity supplied or assigned crew members specifically for a particular type or category of mission.
-
E.
crewMemberInOrbit
Indicates that a person is serving as a crew member aboard a spacecraft or station that is currently in orbit.
- 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_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.