Triple
T14048846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caladan Oceanic deep-sea expeditions |
E338030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deep-sea exploration program |
C34003
|
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: deep-sea exploration program Context triple: [Caladan Oceanic deep-sea expeditions, instanceOf, deep-sea exploration program]
-
A.
deep-sea exploration team
A deep-sea exploration team is a specialized group of scientists, engineers, and support personnel who collaboratively use advanced submersibles and technologies to investigate, map, and study the ocean’s most remote and extreme environments.
-
B.
deep-sea research vehicle
A deep-sea research vehicle is a specialized submersible designed to explore, observe, and collect data and samples from extreme underwater environments at great ocean depths.
-
C.
deep-diving research submersible
A deep-diving research submersible is a specialized, crewed or remotely operated underwater vehicle designed to withstand extreme ocean pressures and carry scientific instruments to explore, observe, and collect data from the deepest parts of the sea.
-
D.
deep-submergence vehicle
A deep-submergence vehicle is a specialized, highly pressure-resistant underwater craft designed to operate at great ocean depths for exploration, research, inspection, or rescue missions.
-
E.
planetary exploration program
A planetary exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study other planets and celestial bodies using robotic or crewed spacecraft.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.