Triple
T29698318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbes Expedition |
E751413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military campaign |
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 military campaign Context triple: [Forbes Expedition, instanceOf, British military campaign]
-
A.
British colonial military operation
A British colonial military operation is a coordinated campaign conducted by British armed forces to establish, maintain, or expand control over territories within the British Empire, often involving combat, occupation, and enforcement of imperial policies.
-
B.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
C.
British military plan
A British military plan is a strategic and operational blueprint developed by the United Kingdom’s armed forces to achieve specific defense or combat objectives through coordinated use of personnel, equipment, and tactics.
-
D.
British-organized force
A British-organized force is a military or paramilitary unit that is raised, structured, trained, equipped, or commanded under the authority or direction of the British government or its agents.
-
E.
British expedition
chosen
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.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:22 p.m.