Triple
T9299348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Kent |
E223719
|
entity |
| Predicate | styleOfAddressForHolder |
P20993
|
FINISHED |
| Object | Your 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: Your Royal Highness | Statement: [Dukedom of Kent, styleOfAddressForHolder, Your Royal Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfAddressForHolder Context triple: [Dukedom of Kent, styleOfAddressForHolder, Your Royal Highness]
-
A.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
B.
isStyleOfAddress
Indicates that one term or expression functions as a particular way of addressing or referring to another entity.
-
C.
usedInStyleOfAddress
Indicates that one entity is used as a form or style of address when referring to or speaking to another entity.
-
D.
officeHolderStyle
chosen
Indicates the formal title, manner of address, or stylistic designation used for a person holding a particular office or position.
-
E.
addresseePosition
Indicates the spatial or positional relationship of the addressee relative to a reference point or speaker.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08cf50cc8190a025f478dff4f9fd |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.