Triple
T28269418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蔣 |
E712801
|
entity |
| Predicate | transliterationInJapaneseKanji |
P133413
|
FINISHED |
| Object | ショウ (Shō) |
—
|
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: ショウ (Shō) | Statement: [蔣, transliterationInJapaneseKanji, ショウ (Shō)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transliterationInJapaneseKanji Context triple: [蔣, transliterationInJapaneseKanji, ショウ (Shō)]
-
A.
equivalentInJapaneseKanji
Indicates that one entity has the same meaning or value as another entity when written in Japanese Kanji.
-
B.
JapaneseNameReading
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other entity.
-
C.
translationOfJapaneseName
Indicates that one entity is a translation of a Japanese name given by the other entity.
-
D.
onYomiJapanese
chosen
Indicates that the specified reading is the on’yomi (Sino-Japanese) pronunciation associated with a given kanji or term.
-
E.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 11:17 p.m.