Triple
T20731314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Regent of Brazil |
E509577
|
entity |
| Predicate | officeHolderTitleStyle |
P20993
|
FINISHED |
| Object | His Royal Highness |
—
|
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: His Royal Highness | Statement: [Prince Regent of Brazil, officeHolderTitleStyle, His Royal Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderTitleStyle Context triple: [Prince Regent of Brazil, officeHolderTitleStyle, His Royal Highness]
-
A.
officeHolderStyle
chosen
Indicates the formal title, manner of address, or stylistic designation used for a person holding a particular office or position.
-
B.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
C.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
D.
officeHolderMayUseTitle
Indicates that a person who holds a particular office is permitted to use a specified official title.
-
E.
typicalOfficeHolderTitle
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ed7e8c8190974f2eb31a0a3106 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:30 p.m.