Triple
T13037945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boetman is die bliksem in |
E326611
|
entity |
| Predicate | author |
P4
|
FINISHED |
| Object | Chris Louw |
E326611
|
NE 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: Chris Louw | Statement: [Boetman is die bliksem in, author, Chris Louw]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chris Louw Context triple: [Boetman is die bliksem in, author, Chris Louw]
-
A.
Chris Louw
chosen
Chris Louw is a South African journalist and writer best known for his provocative open letter "Boetman is die bliksem in" criticizing the apartheid-era Afrikaner establishment.
-
B.
Jaco Louw
Jaco Louw is a notable individual bearing the Afrikaans surname Louw, recognized within contexts where the name has particular cultural or public significance.
-
C.
Robbie Louw
Robbie Louw is the son of former South African rugby union star Rob Louw.
-
D.
Gavin Louw
Gavin Louw is an individual notable enough to be specifically cited as a bearer of the surname Louw.
-
E.
Charl Louw
Charl Louw is an individual notable enough to be recognized as a prominent bearer of the surname Louw.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9804b743c8190810dc5c14bc6d912 |
completed | April 10, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbd12eec81908ad5dae638c2210e |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:55 p.m.