Triple
T24600250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1870 United States census |
E608802
|
entity |
| Predicate | endDateOfEnumeration |
P140
|
FINISHED |
| Object | 1871-05-00 |
—
|
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: 1871-05-00 | Statement: [1870 United States census, endDateOfEnumeration, 1871-05-00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endDateOfEnumeration Context triple: [1870 United States census, endDateOfEnumeration, 1871-05-00]
-
A.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
-
B.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
D.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
E.
fundingPeriodEnd
Indicates the date or point in time when a particular funding arrangement, grant, or financial support comes to an end.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.