Triple
T1620412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossing of the Drakensberg |
E35017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century event in South Africa |
C383
|
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: 19th-century event in South Africa Context triple: [Crossing of the Drakensberg, instanceOf, 19th-century event in South Africa]
-
A.
country in Southern Africa
A country in Southern Africa is a sovereign state located in the southern region of the African continent, typically characterized by shared geographic proximity, regional economic and political ties, and often diverse cultural and linguistic communities.
-
B.
South African person
A South African person is an individual who holds South African nationality or identity, shaped by the country’s diverse cultures, histories, and languages.
-
C.
province of South Africa
A province of South Africa is a primary administrative division of the country, each with its own government structures, geographic boundaries, and socio-economic characteristics under the national constitution.
-
D.
colonial-era event
chosen
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
E.
event in the Crimean War
An event in the Crimean War is a specific historical occurrence—such as a battle, diplomatic action, military maneuver, or political decision—that took place between 1853 and 1856 and contributed to the course and outcome of the conflict.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.