Triple
T33547486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Emeritus of Japan |
E859243
|
entity |
| Predicate | hasAlternativeJapaneseReading |
P143799
|
FINISHED |
| Object | Daijō Tennō |
—
|
NE NERFINISHED |
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: Daijō Tennō | Statement: [Emperor Emeritus of Japan, hasAlternativeJapaneseReading, Daijō Tennō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeJapaneseReading Context triple: [Emperor Emeritus of Japan, hasAlternativeJapaneseReading, Daijō Tennō]
-
A.
alternativeKanjiForm
Indicates that one kanji character or writing is an alternative form of another kanji for the same word or concept.
-
B.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
-
C.
JapaneseNameReading
chosen
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other entity.
-
D.
onYomiJapanese
Indicates that the specified reading is the on’yomi (Sino-Japanese) pronunciation associated with a given kanji or term.
-
E.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 1:39 a.m.