Triple
T35332131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joshua Dunbar |
E1020348
|
entity |
| Predicate | socialStatusBeforeEmancipation |
P24343
|
FINISHED |
| Object | enslaved |
—
|
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 | Statement: [Joshua Dunbar, socialStatusBeforeEmancipation, enslaved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusBeforeEmancipation Context triple: [Joshua Dunbar, socialStatusBeforeEmancipation, enslaved]
-
A.
beneficiariesOfEmancipation
Indicates that the subject is a person or group who gains rights, freedoms, or advantages as a result of an emancipation event or process.
-
B.
emancipatedIn
Indicates that an entity was legally freed or released from bondage, control, or restrictions in a specific place or jurisdiction.
-
C.
legalStatusOfSlavery
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
D.
wasFormerlyEnslaved
chosen
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
E.
legalStatusBefore1791
Indicates the legal status or condition that an entity held prior to the year 1791.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:03 p.m.