Triple
T31490973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1860 United States census |
E803401
|
entity |
| Predicate | slavePopulationCounted |
P32997
|
FINISHED |
| Object | 3934837 |
—
|
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: 3934837 | Statement: [1860 United States census, slavePopulationCounted, 3934837]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slavePopulationCounted Context triple: [1860 United States census, slavePopulationCounted, 3934837]
-
A.
captivePopulation
Indicates that the entities are part of a population kept in captivity, such as in zoos, aquariums, or breeding facilities, rather than living in the wild.
-
B.
lastKnownPopulations
Indicates the most recently recorded population counts associated with an entity or set of entities.
-
C.
populationCount
chosen
Indicates the total number of individuals in a specified group, area, or category.
-
D.
hostsPopulation
Indicates that an entity serves as the living environment or container in which a particular population exists or resides.
-
E.
populationCountedIn
Indicates that the population of one entity is measured, recorded, or included within the population statistics of another entity.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:38 p.m.