Triple
T38479419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Module C-020 |
E915629
|
entity |
| Predicate | crewStatusOnMission |
P51184
|
FINISHED |
| Object | uncrewed |
—
|
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: uncrewed | Statement: [Command Module C-020, crewStatusOnMission, uncrewed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewStatusOnMission Context triple: [Command Module C-020, crewStatusOnMission, uncrewed]
-
A.
crewStatus
chosen
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
-
B.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
C.
crewComplementStatusOnLaunch
Indicates the status or condition of a vehicle’s assigned crew complement at the moment of launch.
-
D.
providedCrewForMissionType
Indicates that an entity supplied or assigned crew members specifically for a particular type or category of mission.
-
E.
commandCrew
Indicates that one entity holds command authority over the crew associated with another entity.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.