Triple

T1684085
Position Surface form Disambiguated ID Type / Status
Subject Middleton Place E36402 entity
Predicate usedEnslavedLabor P27275 FINISHED
Object African and African American enslaved people 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: African and African American enslaved people | Statement: [Middleton Place, usedEnslavedLabor, African and African American enslaved people]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedEnslavedLabor
Context triple: [Middleton Place, usedEnslavedLabor, African and African American enslaved people]
  • 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. usedForcedLabor chosen
    Indicates that an entity compelled people to work against their will, typically under coercion, threat, or without fair compensation.
  • D. populationGroupEnslaved
    Indicates that one population group is held in a condition of slavery or forced servitude by another.
  • E. legalStatusOfSlavery
    Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
  • 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_69a886151508819084fa7f1ce6e05577 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aba644070c81908745b56d981fe273 completed March 7, 2026, 4:15 a.m.
PD Predicate disambiguation batch_69aa61b57a6881909373af287ef24799 completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:29 p.m.