Triple
T20985158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1790 United States census |
E516873
|
entity |
| Predicate | populationCountedAs |
P32997
|
FINISHED |
| Object | 3,929,214 |
—
|
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: 3,929,214 | Statement: [1790 United States census, populationCountedAs, 3,929,214]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationCountedAs Context triple: [1790 United States census, populationCountedAs, 3,929,214]
-
A.
populationCountedDescription
Indicates that a population has been enumerated or measured, with an accompanying description of how or under what conditions the counting was performed.
-
B.
populationCount
chosen
Indicates the total number of individuals in a specified group, area, or category.
-
C.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
D.
populationMeasurementBy
Indicates that a population quantity or statistic is determined, recorded, or reported by a specified agent, method, or source.
-
E.
hostsPopulation
Indicates that an entity serves as the living environment or container in which a particular population exists or resides.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe218748190a987b9f922d9be1b |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.