Triple
T115785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavery Abolition Act 1833 |
E2334
|
entity |
| Predicate | compensationAmount |
P482
|
FINISHED |
| Object | £20,000,000 |
—
|
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: £20,000,000 | Statement: [Slavery Abolition Act 1833, compensationAmount, £20,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compensationAmount Context triple: [Slavery Abolition Act 1833, compensationAmount, £20,000,000]
-
A.
compensationPolicy
Indicates the rules or guidelines that govern how compensation (such as salary, bonuses, or benefits) is determined and provided.
-
B.
salary
Indicates the amount of monetary compensation an entity receives, typically on a regular basis, for work or services performed.
-
C.
monetaryValue
chosen
Indicates the amount of money associated with an entity, event, or transaction.
-
D.
totalAidAmountAdjusted
Indicates the total amount of aid provided, after applying any relevant adjustments such as corrections, discounts, or recalculations.
-
E.
monetaryValueSponsor
Indicates that a sponsor provides or assigns a specific monetary value (amount of funding) to another entity or activity.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.