Triple
T24176788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Sea party |
E599304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical expedition party |
C48333
|
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: historical expedition party Context triple: [Ross Sea party, instanceOf, historical expedition party]
-
A.
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.
-
B.
United States Army expedition
A United States Army expedition is a formally organized, often temporary military operation conducted by the U.S. Army beyond its usual garrison locations to achieve specific strategic, tactical, or exploratory objectives.
-
C.
archaeological expedition
An archaeological expedition is a planned scientific journey undertaken by researchers to locate, excavate, and analyze material remains of past human cultures at specific sites.
-
D.
1968 expedition
A 1968 expedition is a historically situated journey or organized exploration undertaken in the year 1968, typically involving a specific objective such as scientific research, geographic discovery, or cultural investigation.
-
E.
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.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:34 p.m.