Triple
T22139726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hlubi |
E547123
|
entity |
| Predicate | historicalProcessExperienced |
P2107
|
FINISHED |
| Object | colonial 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: colonial dispossession | Statement: [Hlubi, historicalProcessExperienced, colonial dispossession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalProcessExperienced Context triple: [Hlubi, historicalProcessExperienced, colonial dispossession]
-
A.
majorHistoricalProcess
Indicates a large-scale, transformative sequence of events or developments that significantly shapes the course of history.
-
B.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
C.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
D.
historicalCondition
Indicates that one entity represents a condition, state, or circumstance that applied to another entity at some point in the past.
-
E.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bda1208190b851ae5c68b760e9 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.