Triple
T5940340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soweto Uprising |
E132149
|
entity |
| Predicate | languagePolicyProtested |
P33151
|
FINISHED |
| Object | Afrikaans |
—
|
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: Afrikaans | Statement: [Soweto Uprising, languagePolicyProtested, Afrikaans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languagePolicyProtested Context triple: [Soweto Uprising, languagePolicyProtested, Afrikaans]
-
A.
languagePolicyIssue
chosen
Indicates that there is a problem, conflict, or concern related to rules or practices governing language use.
-
B.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
C.
policyLanguage
Indicates the specific wording or formulation used within a policy to express its rules, conditions, or provisions.
-
D.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
E.
languagePolicyRegion
Indicates that a particular language policy applies within, or is associated with, a specific geographic or administrative region.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.