Triple
T18916662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiento de Negros |
E462740
|
entity |
| Predicate | perpetratedHarmOn |
P81195
|
FINISHED |
| Object | enslaved Africans |
—
|
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: enslaved Africans | Statement: [Asiento de Negros, perpetratedHarmOn, enslaved Africans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratedHarmOn Context triple: [Asiento de Negros, perpetratedHarmOn, enslaved Africans]
-
A.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
B.
recognizedHarm
Indicates that an entity has identified or acknowledged the existence or occurrence of harm affecting another entity or situation.
-
C.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
D.
honorsVictimOf
Indicates that one entity pays tribute or respect to another entity who has suffered harm, loss, or injustice.
-
E.
hasPerpetrators
chosen
Indicates that certain entities are responsible for carrying out, committing, or executing a particular act, event, or wrongdoing.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.