Triple
T29206846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1920 United States Census |
E740433
|
entity |
| Predicate | recordsAccessRestrictionPeriod |
P93788
|
FINISHED |
| Object | 72 years |
—
|
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: 72 years | Statement: [1920 United States Census, recordsAccessRestrictionPeriod, 72 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsAccessRestrictionPeriod Context triple: [1920 United States Census, recordsAccessRestrictionPeriod, 72 years]
-
A.
accessRestrictedSince
Indicates that access to an entity has been limited or blocked starting from a specified point in time.
-
B.
accessionPeriod
Indicates the time span during which an entity is formally acquired, admitted, or granted entry into a system, collection, or status.
-
C.
dataRetentionPeriod
chosen
Indicates the length of time data is stored or kept before it is deleted, archived, or otherwise disposed of.
-
D.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
E.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 12:09 p.m.