Triple
T26466719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ball family of South Carolina |
E665786
|
entity |
| Predicate | usedLaborOf |
P93505
|
FINISHED |
| Object | enslaved Africans |
—
|
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: enslaved Africans | Statement: [Ball family of South Carolina, usedLaborOf, enslaved Africans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLaborOf Context triple: [Ball family of South Carolina, usedLaborOf, enslaved Africans]
-
A.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
B.
usedLabourFrom
chosen
Indicates that one entity employed or made use of the labor or work effort provided by another entity.
-
C.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
D.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
E.
laborSet
Indicates that a particular labor, task, or work assignment has been designated or scheduled for an entity 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 12:16 a.m.