Triple
T31424654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1850 United States census |
E801625
|
entity |
| Predicate | slaveSchedulesDataCollected |
P135885
|
FINISHED |
| Object | age of enslaved person |
—
|
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: age of enslaved person | Statement: [1850 United States census, slaveSchedulesDataCollected, age of enslaved person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slaveSchedulesDataCollected Context triple: [1850 United States census, slaveSchedulesDataCollected, age of enslaved person]
-
A.
collectorStatus
Indicates the current operational or lifecycle state of a collector in relation to its collection activity.
-
B.
dataCollectedAt
Indicates that some data was gathered or recorded at a specific time or place.
-
C.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
D.
sampleCollected
Indicates that a sample has been obtained or gathered from a source as part of a collection process.
-
E.
dataCaptured
chosen
Indicates that some form of data has been recorded or collected from a source or process.
- 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.