Triple
T36974894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venda Kingdom |
E914670
|
entity |
| Predicate | ethnoHistoricalRegion |
P126673
|
FINISHED |
| Object | Venda |
—
|
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: Venda | Statement: [Venda Kingdom, ethnoHistoricalRegion, Venda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoHistoricalRegion Context triple: [Venda Kingdom, ethnoHistoricalRegion, Venda]
-
A.
ethnoHistoricRegion
chosen
Indicates a relationship where an entity is associated with a geographic region defined by its historical and ethnic or cultural characteristics.
-
B.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
C.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
-
D.
regionHistoricalEthnonym
Indicates that a region is historically known or referred to by a particular ethnonym associated with a people or ethnic group.
-
E.
ethnicRegionOfFocus
Indicates that a particular ethnic group or ethnicity is the primary regional focus or subject of attention in a given context.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.