Triple
T4903221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire of Brazil |
E109850
|
entity |
| Predicate | abolitionOfMonarchy |
P21968
|
FINISHED |
| Object | 15 November 1889 |
—
|
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: 15 November 1889 | Statement: [Empire of Brazil, abolitionOfMonarchy, 15 November 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolitionOfMonarchy Context triple: [Empire of Brazil, abolitionOfMonarchy, 15 November 1889]
-
A.
monarchyAbolishedIn
chosen
Indicates that a monarchy was officially ended or abolished in a specified place or at a specified time.
-
B.
monarchDeposed
Indicates that a monarch has been removed from power, typically against their will, by force, coercion, or formal deposition.
-
C.
restoredMonarchy
Indicates that an entity caused or participated in the re-establishment of a previously abolished or suspended monarchy.
-
D.
usedBeforeAbolitionOfMonarchy
Indicates that something was in use prior to the abolition of the monarchy.
-
E.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.