Triple
T27075360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 51 |
E685447
|
entity |
| Predicate | cargoSpacecraftVisited |
P162044
|
FINISHED |
| Object | SpaceX CRS-11 |
—
|
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: SpaceX CRS-11 | Statement: [Expedition 51, cargoSpacecraftVisited, SpaceX CRS-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoSpacecraftVisited Context triple: [Expedition 51, cargoSpacecraftVisited, SpaceX CRS-11]
-
A.
cargoSpacecraftVisited
chosen
Indicates that a cargo spacecraft has made a visit to a particular location or object.
-
B.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
-
C.
spaceStationVisit
Indicates that an entity travels to and spends time at a space station as a visitor or temporary occupant.
-
D.
spaceflightVehicleFlown
Indicates that a particular spaceflight vehicle has been operated or flown by a specific agent (such as a person, crew, or organization).
-
E.
spacecraftServedOn
Indicates that a particular spacecraft is one on which an entity (typically a person) has served or been assigned.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 8:31 a.m.