Triple
T1411332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tswana people |
E31810
|
entity |
| Predicate | traditionalLeaderTitle |
P11127
|
FINISHED |
| Object | kgosi |
—
|
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: kgosi | Statement: [Tswana people, traditionalLeaderTitle, kgosi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLeaderTitle Context triple: [Tswana people, traditionalLeaderTitle, kgosi]
-
A.
leaderMayHoldTitle
Indicates that a leader is permitted or able to possess or be designated by a particular formal title.
-
B.
civilianLeaderTitle
Indicates the official title held by a person who serves as the civilian leader of a group, organization, or jurisdiction.
-
C.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
D.
traditionalTitle
chosen
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
E.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e1da988190bc7c187e193539b6 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.