Triple
T31424576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1800 United States census |
E801624
|
entity |
| Predicate | freeWhitePopulation |
P171856
|
FINISHED |
| Object | 4106199 |
—
|
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: 4106199 | Statement: [1800 United States census, freeWhitePopulation, 4106199]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeWhitePopulation Context triple: [1800 United States census, freeWhitePopulation, 4106199]
-
A.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
B.
totalPopulation
Indicates the overall number of individuals in a defined group, area, or category, typically summing all constituent subpopulations.
-
C.
population
Indicates the total number of individuals living in or present within a specified area or group.
-
D.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
E.
populationBasis
Indicates that a population measurement is based on, derived from, or defined with respect to a particular reference, criterion, or underlying basis.
- F. None of above. chosen
Provenance (4 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 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. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 8:51 p.m.