Triple
T8608537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston King |
E203863
|
entity |
| Predicate | wasEnslavedBy |
P55901
|
FINISHED |
| Object | slaveholders in South Carolina |
—
|
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: slaveholders in South Carolina | Statement: [Boston King, wasEnslavedBy, slaveholders in South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEnslavedBy Context triple: [Boston King, wasEnslavedBy, slaveholders in South Carolina]
-
A.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
B.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
C.
hasEnslavedCharacter
chosen
Indicates that one entity has held another entity in a state of slavery or forced servitude.
-
D.
numberOfEnslaved
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given entity or context.
-
E.
populationGroupEnslaved
Indicates that one population group is held in a condition of slavery or forced servitude by another.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ec301881908ce148a3f07069fe |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.