Triple
T31656689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planet Express |
E807874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interplanetary delivery company |
C61417
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: interplanetary delivery company Context triple: [Planet Express, instanceOf, interplanetary delivery company]
-
A.
interplanetary space mission
An interplanetary space mission is a coordinated endeavor that sends spacecraft from one planet to another to conduct scientific research, exploration, or technology demonstration beyond Earth's immediate environment.
-
B.
space mission rideshare platform
A space mission rideshare platform is a digital marketplace that connects satellite operators and payload customers with available launch capacity on rockets, enabling shared missions, cost savings, and streamlined logistics for accessing space.
-
C.
interstellar vessel
An interstellar vessel is a spacecraft designed for sustained travel between star systems, supporting propulsion, navigation, life support, and shielding over vast interstellar distances.
-
D.
ExPRESS Logistics Carrier
The ExPRESS Logistics Carrier is an uncrewed, modular platform attached to the International Space Station that provides power, data, and structural support for external scientific experiments and payloads.
-
E.
space station resupply vehicle
A space station resupply vehicle is a spacecraft designed to transport cargo, equipment, and sometimes crew to and from an orbiting space station, supporting its ongoing operations and maintenance.
- F. None of above. chosen
Provenance (1 batch)
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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:55 p.m.