Triple
T5168949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiento granted to Britain |
E116626
|
entity |
| Predicate | allowedAnnualQuota |
P52204
|
FINISHED |
| Object | 4,800 enslaved Africans 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: 4,800 enslaved Africans per year | Statement: [Asiento granted to Britain, allowedAnnualQuota, 4,800 enslaved Africans per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedAnnualQuota Context triple: [Asiento granted to Britain, allowedAnnualQuota, 4,800 enslaved Africans 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.
annualContainerThroughput
Indicates the total volume of containers handled by a facility or system over the course of a year.
-
D.
isAnnual
Indicates that something occurs, is scheduled, or is valid once every year.
-
E.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794dd9988190922e138f2a9a3c62 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.