Triple
T6426164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Jordan |
E128062
|
entity |
| Predicate | style |
P87
|
FINISHED |
| Object | His Majesty |
E584077
|
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: [King of Jordan, style, His Majesty]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: His Majesty Context triple: [King of Jordan, style, His Majesty]
-
A.
His Majesty
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 Gustav III, the 18th-century King of Sweden known for his enlightened absolutism and cultural patronage.
-
C.
His Majesty the King
His Majesty the King is the formal royal style used to address and refer to the reigning monarch of Thailand.
-
D.
His Majesty The King
His Majesty The King is the formal royal style used to address Carl XVI Gustaf, the reigning King of Sweden.
-
E.
His Majesty The King
chosen
His Majesty The King is the royal style traditionally used to address a reigning male monarch such as a king.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0691f944c81909d4e5d8ef9e494b6 |
completed | March 22, 2026, 10:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c64bbc865c81909bf064b9253bc263 |
completed | March 27, 2026, 9:19 a.m. |
Created at: March 22, 2026, 4:43 p.m.