Triple
T31424604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1800 United States census |
E801624
|
entity |
| Predicate | dataItemsCollected |
P4241
|
FINISHED |
| Object | name of head of household |
—
|
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: name of head of household | Statement: [1800 United States census, dataItemsCollected, name of head of household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataItemsCollected Context triple: [1800 United States census, dataItemsCollected, name of head of household]
-
A.
collectorValue
Indicates that something possesses worth or significance specifically as a collectible item, often due to rarity, condition, or desirability among collectors.
-
B.
collectingStatus
Indicates the current state or phase of an ongoing collection process or activity.
-
C.
collectionSize
Indicates the total number of items contained within a specified collection.
-
D.
dataTypeCollected
chosen
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
E.
yearCellsCollected
Indicates the calendar year in which the cells were collected.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 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 30, 2026, 8:51 p.m.