Triple
T22035567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act Against Slavery (1793) |
E544196
|
entity |
| Predicate | legalStatusOfSlaves |
P6136
|
FINISHED |
| Object | did not free existing enslaved adults |
—
|
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: did not free existing enslaved adults | Statement: [Act Against Slavery (1793), legalStatusOfSlaves, did not free existing enslaved adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfSlaves Context triple: [Act Against Slavery (1793), legalStatusOfSlaves, did not free existing enslaved adults]
-
A.
legalStatusOfSlavery
chosen
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
B.
populationGroupEnslaved
Indicates that one population group is held in a condition of slavery or forced servitude by another.
-
C.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
D.
numberOfEnslaved
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given entity or context.
-
E.
historicalPeriodOfEnslavement
Indicates the specific historical period during which an entity was subjected to enslavement.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f0594881909caf4fbc3e0a2d50 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.