Triple
T1561529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshihito |
E33333
|
entity |
| Predicate | honorificPrefix |
P536
|
FINISHED |
| Object | Emperor |
E2130
|
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: Emperor | Statement: [Yoshihito, honorificPrefix, Emperor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emperor Context triple: [Yoshihito, honorificPrefix, Emperor]
-
A.
Emperor
chosen
The Emperor is the ceremonial monarch and symbolic head of state of Japan, representing the continuity and unity of the Japanese nation.
-
B.
Imperator
Imperator was an ancient Roman title originally meaning "commander" and later associated with the supreme military and political authority of the emperor.
-
C.
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.
-
D.
King of Rome
King of Rome was the title given to Napoleon II, the son and heir of Napoleon Bonaparte, symbolizing his intended role as successor to the French Empire.
-
E.
His Majesty
His Majesty is the formal style of address used for a reigning male British monarch.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9088710a881909a1226e4b54311b8 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad401e12088190b6f0f5b0d8a423cf |
completed | March 8, 2026, 9:23 a.m. |
Created at: March 4, 2026, 7:27 p.m.