Triple
T18700308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayden Survey party |
E457231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States government expedition |
C40661
|
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: United States government expedition Context triple: [Hayden Survey party, instanceOf, United States government expedition]
-
A.
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.
-
B.
British expedition
A British expedition is an organized journey or voyage undertaken by individuals or groups from Britain, typically for purposes such as exploration, scientific research, military objectives, or cultural exchange.
-
C.
Russian naval expedition
A Russian naval expedition is a state-organized maritime operation undertaken by the Russian Navy for purposes such as exploration, power projection, military engagement, or strategic presence beyond home waters.
-
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.
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.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.