Triple
T31397511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1840 United States census |
E800900
|
entity |
| Predicate | originalSchedulesSurviveForAllStates |
P2248
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [1840 United States census, originalSchedulesSurviveForAllStates, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSchedulesSurviveForAllStates Context triple: [1840 United States census, originalSchedulesSurviveForAllStates, false]
-
A.
originalScheduleRelation
Indicates a relationship where one schedule is defined as the original or baseline reference for another schedule or scheduling state.
-
B.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
-
C.
hasSurvivingOriginals
chosen
Indicates that some of the original instances or versions of an entity still exist and have not been lost, destroyed, or replaced.
-
D.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
E.
survivesFromPeriod
Indicates that an entity continues to exist or remain intact from a specified historical or temporal period into a later time.
- 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_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: April 29, 2026, 9:19 p.m.