Triple
T1620527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African general election, 1989 |
E35019
|
entity |
| Predicate | tookPlaceUnder |
P9459
|
FINISHED |
| Object | apartheid system |
—
|
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: apartheid system | Statement: [South African general election, 1989, tookPlaceUnder, apartheid system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceUnder Context triple: [South African general election, 1989, tookPlaceUnder, apartheid system]
-
A.
underAuspicesOf
chosen
Indicates that an action, event, or entity operates under the sponsorship, authority, or guidance of another party.
-
B.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
C.
tookPlaceFrom
Indicates that an event or occurrence started or was ongoing beginning at a specified time or location.
-
D.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
E.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.