Triple
T7057966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orange Free State |
E164141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Boer republic |
C20724
|
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 Boer republic Context triple: [Orange Free State, instanceOf, historical Boer republic]
-
A.
former province of South Africa
A former province of South Africa is an administrative territorial division that existed under earlier constitutional arrangements of the country but has since been restructured, renamed, or dissolved in subsequent political reforms.
-
B.
former Free State
A former Free State is a previously autonomous or semi-autonomous political entity that once held a distinct status as a "Free State" but has since been dissolved, merged, or reclassified within a larger sovereign framework.
-
C.
Bantu state
A Bantu state is a political entity historically or contemporarily governed by Bantu-speaking peoples, typically characterized by centralized authority, kinship-based social organization, and economies rooted in agriculture, herding, and regional trade.
-
D.
former German colony
A former German colony is a territory that was once under the political control and administration of the German Empire or later German states, but has since gained independence or come under another sovereignty.
-
E.
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.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:38 p.m.