Triple
T725615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khoikhoi |
E14718
|
entity |
| Predicate | colonialImpact |
P6677
|
FINISHED |
| Object | land dispossession |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: land dispossession | Statement: [Khoikhoi, colonialImpact, land dispossession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialImpact Context triple: [Khoikhoi, colonialImpact, land dispossession]
-
A.
colonialLegacy
chosen
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
B.
colonialPerception
Indicates how one entity views, interprets, or characterizes another through the lens of colonial power dynamics, assumptions, and hierarchies.
-
C.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
D.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
E.
hadColonialAdministrationType
Indicates the specific form or system of colonial governance that was exercised over a territory or population.
- F. None of above.
Provenance (3 batches)
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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f839608190878a60eb7a044ed9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.