Triple
T21495960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (during Revolutionary War) |
E530351
|
entity |
| Predicate | hadSlavery |
P6136
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [United States (during Revolutionary War), hadSlavery, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSlavery Context triple: [United States (during Revolutionary War), hadSlavery, yes]
-
A.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
B.
legalStatusOfSlavery
chosen
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
C.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
D.
historicalPeriodOfEnslavement
Indicates the specific historical period during which an entity was subjected to enslavement.
-
E.
numberOfEnslaved
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea582d9c8190b95ff6e1b8179b81 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.