Triple
T27039312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbala |
E684442
|
entity |
| Predicate | governingCountryDuringColonialEra |
P4289
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [Mbala, governingCountryDuringColonialEra, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingCountryDuringColonialEra Context triple: [Mbala, governingCountryDuringColonialEra, United Kingdom]
-
A.
partOfColonialEntity
Indicates that one entity is a constituent or subordinate territorial unit within a larger colonial political or administrative entity.
-
B.
colonialPowerOfOrigin
chosen
Indicates the colonial state or empire from which a colony or formerly colonized territory originated or was governed.
-
C.
hasCapitalDuringColonialPeriod
Indicates that a specified location served as the capital of a political entity during its colonial period.
-
D.
wasColonialPower
Indicates that one entity historically exercised colonial control or dominance over another entity.
-
E.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 27, 2026, 8:03 a.m.