Triple
T15871562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bapedi |
E384840
|
entity |
| Predicate | hasChieftaincyStructure |
P120851
|
FINISHED |
| Object | hereditary chieftaincy |
—
|
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: hereditary chieftaincy | Statement: [Bapedi, hasChieftaincyStructure, hereditary chieftaincy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChieftaincyStructure Context triple: [Bapedi, hasChieftaincyStructure, hereditary chieftaincy]
-
A.
hasTribalHeadquarters
Indicates that an entity serves as the official tribal headquarters location for a particular tribe or tribal organization.
-
B.
hasClanChiefResidence
Indicates that a clan has the location where its chief resides or maintains an official dwelling.
-
C.
hasClanChiefStatus
Indicates that an entity holds the role or status of being the chief or leader of a clan.
-
D.
hasTribalAuthority
Indicates that an entity holds recognized governing or decision-making power within a specific tribe or tribal community.
-
E.
hasTribalChairperson
Indicates that an entity is associated with a specific tribal chairperson who serves as its leader or official representative.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.