Triple
T675144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heisei |
E13061
|
entity |
| Predicate | emperorTitle |
P17919
|
FINISHED |
| Object | 125th Emperor of Japan |
—
|
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: 125th Emperor of Japan | Statement: [Heisei, emperorTitle, 125th Emperor of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emperorTitle Context triple: [Heisei, emperorTitle, 125th Emperor of Japan]
-
A.
definedEmperorAs
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
-
B.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
-
C.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
D.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
E.
hasJuniorEmperorTitle
Indicates that an entity holds a subordinate or junior-level emperor title in relation to a higher-ranking imperial authority.
- F. None of above. chosen
Provenance (4 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0266e7c8190a94c4b4b761c59f4 |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49ebf33c481909949526cb8f223dd |
completed | March 1, 2026, 8:17 p.m. |
Created at: March 1, 2026, 7:36 p.m.