Triple
T7845694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Six residents in Cape Town |
E181916
|
entity |
| Predicate | victimOfPolicy |
P50002
|
FINISHED |
| Object | racial segregation |
—
|
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: racial segregation | Statement: [District Six residents in Cape Town, victimOfPolicy, racial segregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimOfPolicy Context triple: [District Six residents in Cape Town, victimOfPolicy, racial segregation]
-
A.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
B.
victimStatus
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
-
C.
isVictimOf
chosen
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
D.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
E.
victimState
Indicates the condition or status that a victim is in as a result of an event, action, or harmful incident.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163d92fc8190a4efcb08d6b3d404 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.