Triple
T31397625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1940 United States census |
E800902
|
entity |
| Predicate | recordsPublicReleaseDate |
P123590
|
FINISHED |
| Object | April 2, 2012 |
—
|
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: April 2, 2012 | Statement: [1940 United States census, recordsPublicReleaseDate, April 2, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsPublicReleaseDate Context triple: [1940 United States census, recordsPublicReleaseDate, April 2, 2012]
-
A.
dataReleaseDate
chosen
Indicates the date on which a particular dataset or piece of data is officially made available or published.
-
B.
businessReleaseDate
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
-
C.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
D.
dataReleaseYear
Indicates the year in which the data was officially released or made publicly available.
-
E.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 29, 2026, 9:19 p.m.