Triple
T12824953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshinobu |
E306624
|
entity |
| Predicate | possibleKanjiMeaning |
P106549
|
FINISHED |
| Object | good |
—
|
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: good | Statement: [Yoshinobu, possibleKanjiMeaning, good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleKanjiMeaning Context triple: [Yoshinobu, possibleKanjiMeaning, good]
-
A.
typicalKanjiMeaning
Indicates that one entity is the standard or commonly accepted meaning associated with a given kanji character.
-
B.
meaningDependsOnKanji
Indicates that the meaning of something (e.g., a word or expression) is determined by, or varies according to, the specific kanji characters used.
-
C.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
D.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
-
E.
commonKanjiComponent
Indicates that two or more kanji share a common graphical component or radical in their written form.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96edcc99c8190986cd78fe4714835 |
completed | April 10, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:32 p.m.