Triple
T37934122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian monarchist movement |
E946298
|
entity |
| Predicate | favoredDynasty |
P85145
|
FINISHED |
| Object | House of Orléans-Braganza |
—
|
NE NERFINISHED |
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: House of Orléans-Braganza | Statement: [Brazilian monarchist movement, favoredDynasty, House of Orléans-Braganza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: favoredDynasty Context triple: [Brazilian monarchist movement, favoredDynasty, House of Orléans-Braganza]
-
A.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
-
B.
dynasticHouseFavored
chosen
Indicates that a particular dynastic house is preferred, supported, or given special favor in a political, social, or succession context.
-
C.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
D.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
E.
nominalDynasty
Indicates that one entity is the nominal or titular ruling dynasty associated with another entity, such as a state, period, or domain.
- 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_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.