Triple
T6068995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Most Christian Majesty |
E135230
|
entity |
| Predicate | hasFormOfAddressType |
P64298
|
FINISHED |
| Object | majesty style |
—
|
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: majesty style | Statement: [His Most Christian Majesty, hasFormOfAddressType, majesty style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormOfAddressType Context triple: [His Most Christian Majesty, hasFormOfAddressType, majesty style]
-
A.
isStyleOfAddress
Indicates that one term or expression functions as a particular way of addressing or referring to another entity.
-
B.
mediaFormOfAddress
Indicates how something is referred to or addressed within a media context (e.g., title, style, or mode of address used in media).
-
C.
usedInStyleOfAddress
chosen
Indicates that one entity is used as a form or style of address when referring to or speaking to another entity.
-
D.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
E.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0574157848190bb8e0972eb55a363 |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.