Triple
T2872022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afro-Saint Kitts and Nevis people |
E63584
|
entity |
| Predicate | historicalPeriodOfEnslavement |
P43443
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Afro-Saint Kitts and Nevis people, historicalPeriodOfEnslavement, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfEnslavement Context triple: [Afro-Saint Kitts and Nevis people, historicalPeriodOfEnslavement, 17th century]
-
A.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
B.
populationGroupEnslaved
Indicates that one population group is held in a condition of slavery or forced servitude by another.
-
C.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
D.
legalStatusOfSlavery
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
E.
positionOnSlavery
Indicates a stance, opinion, or policy that an entity holds regarding the institution or practice of slavery.
- F. None of above. chosen
Provenance (4 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe46a1c819084399a191f0dfe9c |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.