Triple
T38044817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom Space |
E949587
|
entity |
| Predicate | AxiomMission2Spacecraft |
P148889
|
FINISHED |
| Object | Crew Dragon |
—
|
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: Crew Dragon | Statement: [Axiom Space, AxiomMission2Spacecraft, Crew Dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AxiomMission2Spacecraft Context triple: [Axiom Space, AxiomMission2Spacecraft, Crew Dragon]
-
A.
spacecraftOfMission
chosen
Indicates that a given spacecraft is the one used or assigned for a particular mission.
-
B.
spacecraftServedOn
Indicates that a particular spacecraft is one on which an entity (typically a person) has served or been assigned.
-
C.
associatedShuttleMission
Indicates that there is a relationship linking something (e.g., an object, event, or record) to a specific space shuttle mission with which it is connected or involved.
-
D.
volareMissionAssociatedWith
Indicates that a Volare mission is linked or connected to another entity through an association or involvement relationship.
-
E.
cargoMission
Indicates a mission whose primary purpose is to transport cargo from one location to another.
- 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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:20 p.m.