Triple
T33094674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-54 |
E846876
|
entity |
| Predicate | EVACrewMember |
P30830
|
FINISHED |
| Object | Gregory J. Harbaugh |
—
|
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: Gregory J. Harbaugh | Statement: [STS-54, EVACrewMember, Gregory J. Harbaugh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVACrewMember Context triple: [STS-54, EVACrewMember, Gregory J. Harbaugh]
-
A.
crewEVA
Indicates that a crew member performs or participates in an extravehicular activity (spacewalk) outside their spacecraft.
-
B.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
-
C.
EVAcrew
chosen
Indicates that the subject is a crew member participating in an extravehicular activity (spacewalk).
-
D.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
E.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a7c6348190bc2f40bdf6597288 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.