Triple
T8467941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Per Centum Limit Act of 1921 |
E200210
|
entity |
| Predicate | annualNumericalCap |
P52204
|
FINISHED |
| Object | approximately 357,000 immigrants per year |
—
|
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: approximately 357,000 immigrants per year | Statement: [Per Centum Limit Act of 1921, annualNumericalCap, approximately 357,000 immigrants per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualNumericalCap Context triple: [Per Centum Limit Act of 1921, annualNumericalCap, approximately 357,000 immigrants per year]
-
A.
annualQuotaNumber
chosen
Indicates the specific numeric value assigned as an entity’s quota for a given year.
-
B.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
C.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
D.
isAnnual
Indicates that something occurs, is scheduled, or is valid once every year.
-
E.
hasNumberInYear
Indicates that a specific number is associated with or occurs within a given year.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d445f48190884df64bb1aebd41 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.