Triple
T8535463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1890 United States Census |
E202066
|
entity |
| Predicate | censusDate |
P292
|
FINISHED |
| Object | 1890-06-01 |
—
|
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: 1890-06-01 | Statement: [1890 United States Census, censusDate, 1890-06-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censusDate Context triple: [1890 United States Census, censusDate, 1890-06-01]
-
A.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
B.
census
Indicates that an official count or survey is conducted to determine the number and characteristics of a population within a defined area or group.
-
C.
populationCensusYear
chosen
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
D.
censusReportedIn
Indicates that information about a population or demographic count is documented or recorded in a specific census.
-
E.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a295c88190a432a060ee73f04e |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.