Triple
T37934009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lei Áurea |
E946295
|
entity |
| Predicate | replacedLegalStatus |
P197723
|
FINISHED |
| Object | enslaved persons in Brazil |
—
|
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: enslaved persons in Brazil | Statement: [Lei Áurea, replacedLegalStatus, enslaved persons in Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedLegalStatus Context triple: [Lei Áurea, replacedLegalStatus, enslaved persons in Brazil]
-
A.
replacedStatus
Indicates that one entity has taken the place of another, marking the original as superseded or no longer current.
-
B.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
-
C.
legalStatusAfterRenaming
Indicates the legal status or classification that applies to an entity after it has undergone a renaming.
-
D.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
E.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
- F. None of above. chosen
Provenance (4 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_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:20 p.m.