Triple
T17761809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Clarence and St Andrews |
E443394
|
entity |
| Predicate | nobleStyleOfAddress |
P2097
|
FINISHED |
| Object | Her 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: Her Royal Highness | Statement: [Duchess of Clarence and St Andrews, nobleStyleOfAddress, Her Royal Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleStyleOfAddress Context triple: [Duchess of Clarence and St Andrews, nobleStyleOfAddress, Her Royal Highness]
-
A.
nobleTitleStyle
Indicates the specific form or style in which a person's noble title is expressed or formally rendered.
-
B.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
C.
traditionalCourtesyTitleHeir
Indicates that one entity holds the customary or historically recognized courtesy title associated with being the heir of another entity.
-
D.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
E.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485f7a8e08190a4a6b8368b70c381 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:11 a.m.