Triple
T17202387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jannie Malan |
E417507
|
entity |
| Predicate | sharesSurnameWithProminentFiguresIn |
P13741
|
FINISHED |
| Object | South African politics |
—
|
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: South African politics | Statement: [Jannie Malan, sharesSurnameWithProminentFiguresIn, South African politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSurnameWithProminentFiguresIn Context triple: [Jannie Malan, sharesSurnameWithProminentFiguresIn, South African politics]
-
A.
hasLastNameInCommonWith
chosen
Indicates that two entities share the same last name.
-
B.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
C.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
-
D.
sharesEponymWith
Indicates that two entities are named after the same person, place, or thing (i.e., they share the same eponym).
-
E.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db014b08190b88a5001e9f7811b |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.