Triple
T24285726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midori no Hi |
E605663
|
entity |
| Predicate | hasKanjiWriting |
P114914
|
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: [Midori no Hi, hasKanjiWriting, みどりの日（緑の日）]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKanjiWriting Context triple: [Midori no Hi, hasKanjiWriting, みどりの日（緑の日）]
-
A.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
-
B.
canBeWrittenAsKana
Indicates that something (typically text or a term) is able to be represented using Japanese kana characters.
-
C.
hasNameInKanji
chosen
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
D.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
E.
usesKanjiFrom
Indicates that one writing system, word, or text incorporates or is composed of kanji characters originating from another specified source.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5605f081908367bd08ab1ec9ab |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.