Triple
T725598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khoikhoi |
E14718
|
entity |
| Predicate | historicalExonymStatus |
P17110
|
FINISHED |
| Object | pejorative |
—
|
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: pejorative | Statement: [Khoikhoi, historicalExonymStatus, pejorative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalExonymStatus Context triple: [Khoikhoi, historicalExonymStatus, pejorative]
-
A.
exonymStatus
chosen
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
B.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
C.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
D.
colonialExonymSource
Indicates that a name or term is derived from, or originates in, a colonial-era exonym imposed by an external colonial power.
-
E.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f839608190878a60eb7a044ed9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.