Triple
T37327446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of the Abruzzi |
E926647
|
entity |
| Predicate | bearerTitleStyle |
P144332
|
FINISHED |
| Object | His Royal Highness |
—
|
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: His Royal Highness | Statement: [Duke of the Abruzzi, bearerTitleStyle, His Royal Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerTitleStyle Context triple: [Duke of the Abruzzi, bearerTitleStyle, His Royal Highness]
-
A.
bearerTitle
Indicates that one entity holds or is designated by a specific formal title associated with a role, rank, or position.
-
B.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
C.
styleOfTitle
Indicates the stylistic form or presentation type applied to a title (e.g., how the title is formatted or expressed).
-
D.
titleStyleInFull
Indicates that the specified title is presented in its complete, unabridged form, including all stylistic elements or formatting.
-
E.
associatedTitleStyle
chosen
Indicates a relationship where one entity is linked to a particular title style that defines how its title should be presented or formatted.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.