Triple
T23647520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Majesty The King |
E584077
|
entity |
| Predicate | hasHonorificPart |
P368
|
FINISHED |
| Object | His Majesty |
—
|
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: His Majesty | Statement: [His Majesty The King, hasHonorificPart, His Majesty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorificPart Context triple: [His Majesty The King, hasHonorificPart, His Majesty]
-
A.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
B.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
-
C.
hasHonorificPrefix
chosen
Indicates that one entity is used as an honorific title or prefix attached to another entity’s name.
-
D.
hasHonorificNameIn
Indicates that an entity is referred to by a specific honorific or respectful name within a particular language, culture, or contextual setting.
-
E.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28643348190add3666638951680 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.