Triple
T7491068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1955 British Kangchenjunga expedition |
E177005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British expedition |
C22454
|
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: British expedition Context triple: [1955 British Kangchenjunga expedition, instanceOf, British expedition]
-
A.
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.
-
B.
Mir expedition
The Mir expedition class represents a long-duration crewed mission to the Mir space station, encompassing its objectives, crew, timeline, activities, and outcomes.
-
C.
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.
-
D.
British offensive
A British offensive is a coordinated military campaign initiated by British armed forces to attack and weaken enemy positions, gain territory, or achieve specific strategic objectives.
-
E.
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.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:43 p.m.