Triple
T12273078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xesibe |
E292518
|
entity |
| Predicate | belongsToBroaderCategory |
P8622
|
FINISHED |
| Object | Southern African ethnic groups |
—
|
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: Southern African ethnic groups | Statement: [Xesibe, belongsToBroaderCategory, Southern African ethnic groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToBroaderCategory Context triple: [Xesibe, belongsToBroaderCategory, Southern African ethnic groups]
-
A.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
B.
hasParentCategory
chosen
Indicates that an entity belongs to or is organized under a broader, more general category.
-
C.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
D.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
E.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.