Triple
T2082932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 United States census |
E45283
|
entity |
| Predicate | dataCollectionMethod |
P9384
|
FINISHED |
| Object | mail-out mail-back questionnaire |
—
|
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: mail-out mail-back questionnaire | Statement: [2010 United States census, dataCollectionMethod, mail-out mail-back questionnaire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionMethod Context triple: [2010 United States census, dataCollectionMethod, mail-out mail-back questionnaire]
-
A.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
B.
currentCollectionMethod
Indicates the method or process currently being used to collect something (such as data, payments, or materials) from an entity.
-
C.
collectedThrough
chosen
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
D.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
E.
surveyMethod
Indicates the technique or procedure used to conduct a survey or collect survey data.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba5097ac8190a723a8af2982238c |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.