Triple
T2640453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matabeleland |
E62851
|
entity |
| Predicate | colonialDesignation |
P42435
|
FINISHED |
| Object | part of Southern Rhodesia |
—
|
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: part of Southern Rhodesia | Statement: [Matabeleland, colonialDesignation, part of Southern Rhodesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialDesignation Context triple: [Matabeleland, colonialDesignation, part of Southern Rhodesia]
-
A.
colonialOffshoot
Indicates that one entity originated as a colony or derivative settlement established by another entity.
-
B.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
isColonialFoundationOf
Indicates that one entity was established as a colony that later developed into or served as the origin of the other entity.
-
D.
colonialNameUsedBy
Indicates that a colonial-era name for a place, group, or entity is used or applied by a particular agent or source.
-
E.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
- F. None of above. chosen
Provenance (4 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8fc8ee881908a9f6820d8934a62 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:53 p.m.