Triple
T31397668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 United States census |
E800903
|
entity |
| Predicate | includesLongFormQuestionnaire |
P12776
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1980 United States census, includesLongFormQuestionnaire, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLongFormQuestionnaire Context triple: [1980 United States census, includesLongFormQuestionnaire, true]
-
A.
questionnaireType
Indicates the specific category or kind of questionnaire associated with an entity or interaction.
-
B.
usesSurveyOf
Indicates that one entity bases its work, analysis, or decision on data or findings obtained from a particular survey conducted by another entity.
-
C.
includesWildForm
Indicates that something contains or encompasses a wild or non-domesticated form of another entity.
-
D.
containsForm
chosen
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
E.
includesQuestion
Indicates that one entity contains or incorporates a question directed toward or about another entity.
- 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_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:19 p.m.