Triple
T8468050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1910 United States Census |
E200212
|
entity |
| Predicate | populationCountApproximate |
P3412
|
FINISHED |
| Object | 92.2 million |
—
|
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: 92.2 million | Statement: [1910 United States Census, populationCountApproximate, 92.2 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationCountApproximate Context triple: [1910 United States Census, populationCountApproximate, 92.2 million]
-
A.
populationCount
Indicates the total number of individuals in a specified group, area, or category.
-
B.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
C.
populationMeasurementBy
Indicates that a population quantity or statistic is determined, recorded, or reported by a specified agent, method, or source.
-
D.
populationConcentration
Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
-
E.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d445f48190884df64bb1aebd41 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.