Triple
T12929555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charl Louw |
E309337
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Charl Louw |
E309337
|
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: Charl Louw | Statement: [Charl Louw, name, Charl Louw]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Charl Louw Context triple: [Charl Louw, name, Charl Louw]
-
A.
Charl Louw
chosen
Charl Louw is an individual notable enough to be recognized as a prominent bearer of the surname Louw.
-
B.
Danie Louw
Danie Louw is a notable individual recognized for achievements significant enough to be associated with the surname Louw.
-
C.
Niel Louw
Niel Louw is an individual notable enough to be recognized as a prominent bearer of the surname Louw.
-
D.
Rob Louw
Rob Louw is a former South African rugby union flanker renowned for his dynamic play for Western Province and the Springboks during the late 1970s and 1980s.
-
E.
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.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971ec72a48190aceef10630603d2c |
completed | April 10, 2026, 9:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6af687f548190b70ac8fa9bbbd414 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 9, 2026, 5:42 p.m.