Triple
T31397459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1840 United States census |
E800900
|
entity |
| Predicate | enslavedPopulationCount |
P56455
|
FINISHED |
| Object | 2457255 |
—
|
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: 2457255 | Statement: [1840 United States census, enslavedPopulationCount, 2457255]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enslavedPopulationCount Context triple: [1840 United States census, enslavedPopulationCount, 2457255]
-
A.
numberOfEnslaved
chosen
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given entity or context.
-
B.
populationGroupEnslaved
Indicates that one population group is held in a condition of slavery or forced servitude by another.
-
C.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
D.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
E.
numberOfEnslavedPeopleFreed
Indicates the quantity of enslaved individuals who were liberated or set free as a result of a particular action, event, or circumstance.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.