Triple
T20675892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Antarctic Expedition |
E508158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific expedition program |
C3087
|
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: scientific expedition program Context triple: [Russian Antarctic Expedition, instanceOf, scientific expedition program]
-
A.
scientific expedition record
A scientific expedition record is a documented account that systematically captures the objectives, methods, observations, data, and outcomes of a specific scientific journey or field investigation.
-
B.
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.
-
C.
deep-sea exploration program
A deep-sea exploration program is an organized, long-term initiative that uses specialized technologies and scientific methods to investigate, map, and understand the physical, biological, and geological characteristics of the ocean’s deepest regions.
-
D.
scientific endeavor
chosen
A scientific endeavor is a systematic, evidence-based pursuit aimed at discovering, explaining, and predicting natural or social phenomena through observation, experimentation, and critical analysis.
-
E.
manned submersible expedition program
A manned submersible expedition program is an organized, multi-mission initiative that plans, operates, and supports crewed underwater vehicles to explore, study, and document the deep ocean environment.
- F. None of above.
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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:44 a.m.