Triple
T34196535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barotse Province |
E877256
|
entity |
| Predicate | historicalTerritoryWithin |
P24920
|
FINISHED |
| Object | Zambezi basin |
—
|
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: Zambezi basin | Statement: [Barotse Province, historicalTerritoryWithin, Zambezi basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTerritoryWithin Context triple: [Barotse Province, historicalTerritoryWithin, Zambezi basin]
-
A.
historicalTerritoryType
Indicates that a territory is classified according to a specific type or category it held during a historical period.
-
B.
hasHistoricTerritory
chosen
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
C.
hasHistoricalTerritoryNear
Indicates that an entity historically controlled or claimed territory in geographic proximity to another specified location or region.
-
D.
wasCoreTerritoryOf
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
E.
territoryLaterControlledBy
Indicates that a territory was subsequently governed, ruled, or administered by a specified controlling entity after an earlier period.
- 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_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: May 1, 2026, 1:55 a.m.