Triple
T8138981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantu Authorities Act |
E190040
|
entity |
| Predicate | repealContext |
P76477
|
FINISHED |
| Object | end of apartheid |
—
|
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: end of apartheid | Statement: [Bantu Authorities Act, repealContext, end of apartheid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repealContext Context triple: [Bantu Authorities Act, repealContext, end of apartheid]
-
A.
repealProcess
Indicates the process by which an existing law, rule, or regulation is formally revoked or annulled.
-
B.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
C.
repealEffect
chosen
Indicates that one legal act or decision nullifies, cancels, or removes the force or applicability of another.
-
D.
repealedUnder
Indicates that one legal rule, law, or regulation has been formally revoked or annulled by virtue of another specified legal authority or provision.
-
E.
canRepeal
Indicates that one entity has the authority or power to revoke, annul, or cancel a rule, decision, or action established by another entity.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4403cd348190a66ca9ee70d750fb |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.