Triple
T2842360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afro-Antiguans and Barbudans |
E62497
|
entity |
| Predicate | slaveEmancipation |
P6171
|
FINISHED |
| Object | 1834 |
—
|
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: 1834 | Statement: [Afro-Antiguans and Barbudans, slaveEmancipation, 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slaveEmancipation Context triple: [Afro-Antiguans and Barbudans, slaveEmancipation, 1834]
-
A.
beneficiariesOfEmancipation
chosen
Indicates that the subject is a person or group who gains rights, freedoms, or advantages as a result of an emancipation event or process.
-
B.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
C.
slaveryAbolishedBy
Indicates that an instance of slavery was ended, prohibited, or legally abolished by a particular agent, authority, or entity.
-
D.
afterAbolition
Indicates that one event, condition, or state occurs subsequent to the formal ending or abolition of another practice, system, or institution.
-
E.
finalAbolition
Indicates the complete and permanent elimination of something, such that it no longer exists or is practiced in any form.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1898748190b031a2bd2091c0c0 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.