Triple
T21677047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naturalization Act of 1795 |
E534997
|
entity |
| Predicate | changedResidencyRequirementToYears |
P145408
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Naturalization Act of 1795, changedResidencyRequirementToYears, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedResidencyRequirementToYears Context triple: [Naturalization Act of 1795, changedResidencyRequirementToYears, 5]
-
A.
yearOfPermanentResidency
Indicates the specific year in which an entity began or was granted permanent residency in a particular place.
-
B.
residencyDuration
Indicates the length of time an entity has continuously resided or stayed in a particular place or jurisdiction.
-
C.
mainResidencePeriod
Indicates the time span during which a particular place serves as an entity’s primary or main residence.
-
D.
succeededByResidence
Indicates that one residence directly follows and replaces another as the primary place of dwelling for an entity.
-
E.
periodOfResidenceStart
Indicates the date or point in time when an entity’s period of residence at a particular place begins.
- F. None of above. chosen
Provenance (4 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a105b888190820b894d16c1ab77 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:42 p.m.