Triple
T872240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geytie Maria du Plessis |
E18838
|
entity |
| Predicate | spouseOfPositionHolder |
P13
|
FINISHED |
| Object | President of the South African Republic |
—
|
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: President of the South African Republic | Statement: [Geytie Maria du Plessis, spouseOfPositionHolder, President of the South African Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfPositionHolder Context triple: [Geytie Maria du Plessis, spouseOfPositionHolder, President of the South African Republic]
-
A.
spouseOfHonouree
Indicates that one person is the spouse (married partner) of the honouree.
-
B.
firstHolderSpouseOf
Indicates that the first holder in the relation is the spouse (married partner) of the other holder.
-
C.
spouse
chosen
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
D.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
E.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac96850881908a2d776685126137 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.