Triple
T36792565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | amaHlubi of KwaZulu-Natal |
E909093
|
entity |
| Predicate | languageAlsoUse |
P18209
|
FINISHED |
| Object | isiZulu |
—
|
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: isiZulu | Statement: [amaHlubi of KwaZulu-Natal, languageAlsoUse, isiZulu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageAlsoUse Context triple: [amaHlubi of KwaZulu-Natal, languageAlsoUse, isiZulu]
-
A.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
B.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
C.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
D.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
E.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: May 3, 2026, 4:12 p.m.