Triple
T37637022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xhosa Kingdom |
E936515
|
entity |
| Predicate | foundingEthnonym |
P199609
|
FINISHED |
| Object | amaXhosa |
—
|
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: amaXhosa | Statement: [Xhosa Kingdom, foundingEthnonym, amaXhosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingEthnonym Context triple: [Xhosa Kingdom, foundingEthnonym, amaXhosa]
-
A.
ethnonymRoot
Indicates that one term serves as the morphological or etymological root from which an ethnonym (a name for an ethnic group or people) is derived.
-
B.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
C.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
D.
isEthnonymFor
Indicates that one term is the ethnonym (name of a people or ethnic group) used to refer to another entity.
-
E.
ethnonymSingular
Indicates that the subject is the singular form of an ethnonym (a name for a member of a specific ethnic or national group).
- F. None of above. chosen
Provenance (4 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: May 3, 2026, 4:18 p.m.