Triple
T37934152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian monarchist movement |
E946298
|
entity |
| Predicate | proposesHeadOfStateRole |
P38852
|
FINISHED |
| Object | non-partisan monarch |
—
|
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: non-partisan monarch | Statement: [Brazilian monarchist movement, proposesHeadOfStateRole, non-partisan monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesHeadOfStateRole Context triple: [Brazilian monarchist movement, proposesHeadOfStateRole, non-partisan monarch]
-
A.
headOfStateElectionRole
Indicates the role an entity plays in the process of electing or selecting a head of state.
-
B.
proposedMonarch
chosen
Indicates that one entity has been put forward or nominated to become the monarch or ruler of another entity.
-
C.
namedForPoliticalRole
Indicates that one entity is named after another entity specifically because of that entity’s political office, position, or role.
-
D.
nominatingPresident
Indicates that one entity formally selects or proposes another entity to serve as president.
-
E.
hasHeadOfGovernmentCandidate
Indicates that an entity has a specific individual who is a candidate for the position of head of government.
- 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.