Triple
T31397695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 United States census |
E800903
|
entity |
| Predicate | dataDisseminationFormat |
P50897
|
FINISHED |
| Object | printed reports |
—
|
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: printed reports | Statement: [1980 United States census, dataDisseminationFormat, printed reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataDisseminationFormat Context triple: [1980 United States census, dataDisseminationFormat, printed reports]
-
A.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
-
B.
distributedFormat
chosen
Indicates that an entity is made available or disseminated in a particular format or medium.
-
C.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
openFormat
Indicates that an entity is presented or made available in a format that is open, accessible, and not restricted by proprietary constraints.
- 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_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.