Triple
T1868262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John |
E34971
|
entity |
| Predicate | style |
P87
|
FINISHED |
| Object | His Majesty |
E4827
|
NE 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: [John, style, His Majesty]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: His Majesty Context triple: [John, style, His Majesty]
-
A.
His Majesty
chosen
His Majesty is the formal style of address used for a reigning male British monarch.
-
B.
His Majesty the King
His Majesty the King is the formal royal style used to address and refer to the reigning monarch of Thailand.
-
C.
Her Majesty
Her Majesty is the formal royal style used to address or refer to a reigning queen such as Anne, Queen of Great Britain.
-
D.
His Imperial Majesty
"His Imperial Majesty" is a formal honorific style traditionally used to address or refer to a reigning emperor, particularly in the context of the Holy Roman Empire.
-
E.
His Royal Highness
His Royal Highness is a formal style used to address or refer to certain members of a royal family, typically princes and princesses.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb0b6ac108190921c197abc5ab5b5 |
completed | March 7, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69add1d8dd8881909189029a047bc2b4 |
completed | March 8, 2026, 7:45 p.m. |
Created at: March 4, 2026, 7:34 p.m.