Triple
T34196527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barotse Province |
E877256
|
entity |
| Predicate | recognizedTraditionalKingdom |
P87130
|
FINISHED |
| Object | Barotseland 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: Barotseland Kingdom | Statement: [Barotse Province, recognizedTraditionalKingdom, Barotseland Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedTraditionalKingdom Context triple: [Barotse Province, recognizedTraditionalKingdom, Barotseland Kingdom]
-
A.
recognizedAsKingdom
chosen
Indicates that an entity is formally acknowledged or classified as a kingdom within a given system or context.
-
B.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
C.
kingdomAssociatedWith
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
D.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
-
E.
hasTraditionalRulers
Indicates that one entity possesses or is governed by traditional rulers associated with it.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:55 a.m.