Triple
T3134945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afro-Curacaoans |
E65504
|
entity |
| Predicate | historicallyEnslavedBy |
P13391
|
FINISHED |
| Object | Dutch colonists |
—
|
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: Dutch colonists | Statement: [Afro-Curacaoans, historicallyEnslavedBy, Dutch colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyEnslavedBy Context triple: [Afro-Curacaoans, historicallyEnslavedBy, Dutch colonists]
-
A.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
B.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
C.
populationGroupEnslaved
chosen
Indicates that one population group is held in a condition of slavery or forced servitude by another.
-
D.
historicalPeriodOfEnslavement
Indicates the specific historical period during which an entity was subjected to enslavement.
-
E.
wasSlaveDescendant
Indicates that one entity is a descendant of another individual who lived in a condition of slavery.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.