Triple
T37934025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lei Áurea |
E946295
|
entity |
| Predicate | compensationToSlaveowners |
P6170
|
FINISHED |
| Object | none specified |
—
|
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: none specified | Statement: [Lei Áurea, compensationToSlaveowners, none specified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compensationToSlaveowners Context triple: [Lei Áurea, compensationToSlaveowners, none specified]
-
A.
compensationToFormerEnslaved
Indicates that some form of payment or reparative benefit is provided to individuals who were formerly enslaved.
-
B.
compensationToSlaveOwners
chosen
Indicates that compensation is paid to slave owners, typically in relation to the loss or emancipation of enslaved people.
-
C.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
D.
numberOfEnslaved
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given entity or context.
-
E.
capitalUntilAbolition
Indicates that an entity served as the capital of another entity up until the point when that capital status was formally abolished.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:20 p.m.