Triple
T22493581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excelentísima Señora Duquesa |
E556080
|
entity |
| Predicate | equivalentHonorificInEnglish |
P90277
|
FINISHED |
| Object | Most Excellent Lady Duchess |
—
|
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: Most Excellent Lady Duchess | Statement: [Excelentísima Señora Duquesa, equivalentHonorificInEnglish, Most Excellent Lady Duchess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentHonorificInEnglish Context triple: [Excelentísima Señora Duquesa, equivalentHonorificInEnglish, Most Excellent Lady Duchess]
-
A.
alternativeHonorificFor
chosen
Indicates that one honorific title can be used as an alternative form of address for another honorific.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
D.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
E.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb0dfb88190a4175e5e95d7ad4b |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.