Triple
T305138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiwa |
E6280
|
entity |
| Predicate | kanjiCharacters |
P7512
|
FINISHED |
| Object | 令和 |
—
|
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: 令和 | Statement: [Reiwa, kanjiCharacters, 令和]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kanjiCharacters Context triple: [Reiwa, kanjiCharacters, 令和]
-
A.
usesKanjiFrom
Indicates that one writing system, word, or text incorporates or is composed of kanji characters originating from another specified source.
-
B.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
C.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
D.
kun’yomiDerivedFrom
Indicates that a Japanese kun’yomi (native Japanese reading of a kanji) originates from or is historically derived from another form, source, or expression.
-
E.
eraNameInJapanese
chosen
Indicates the Japanese-language name used for a specific historical or calendar era.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea11c4908190a8723033bdf6f479 |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.