Triple
T25949337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantis Expedition |
E653926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multinational expedition |
C50139
|
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: multinational expedition Context triple: [Atlantis Expedition, instanceOf, multinational expedition]
-
A.
historical expedition party
A historical expedition party is a group of individuals organized in the past to undertake a significant journey or exploration, often for purposes of discovery, trade, conquest, or scientific investigation.
-
B.
overland expedition
An overland expedition is a long-distance journey across remote or challenging terrain, typically using rugged vehicles or pack animals, focused on exploration, self-sufficiency, and adventure rather than speed or directness of route.
-
C.
United States government expedition
A United States government expedition is an officially sanctioned and funded journey or mission undertaken by federal agencies to explore, survey, research, or accomplish specific governmental objectives within or beyond U.S. territory.
-
D.
maritime expedition
A maritime expedition is an organized sea voyage undertaken for a specific purpose such as exploration, research, trade, or military objectives, typically involving specialized vessels, crew, and logistical planning.
-
E.
mountaineering expedition
A mountaineering expedition is an organized journey by a team to plan, approach, and ascend challenging mountain terrain, managing technical, environmental, and logistical risks to reach specific climbing objectives.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:43 a.m.