Triple
T35185664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Brazil |
E1015976
|
entity |
| Predicate | slaveryAbolishedOn |
P14067
|
FINISHED |
| Object | 1888-05-13 |
—
|
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: 1888-05-13 | Statement: [History of Brazil, slaveryAbolishedOn, 1888-05-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slaveryAbolishedOn Context triple: [History of Brazil, slaveryAbolishedOn, 1888-05-13]
-
A.
slaveryAbolishedBy
Indicates that an instance of slavery was ended, prohibited, or legally abolished by a particular agent, authority, or entity.
-
B.
afterAbolition
Indicates that one event, condition, or state occurs subsequent to the formal ending or abolition of another practice, system, or institution.
-
C.
hasAbolitionistHistory
Indicates that an entity has a historical association with efforts to abolish a particular practice, system, or institution (commonly slavery or similar forms of oppression).
-
D.
liberationDate
chosen
Indicates the date on which an entity was freed, released, or liberated from a prior state of control, confinement, or oppression.
-
E.
countryOfSlavery
Indicates the country in which an entity was subjected to slavery or enslaved conditions.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dc26cc0819097f39a5d04037670 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.