Triple
T3583126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 近藤信竹 |
E75846
|
entity |
| Predicate | よみがな |
P9812
|
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: [近藤信竹, よみがな, こんどう のぶたけ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: よみがな Context triple: [近藤信竹, よみがな, こんどう のぶたけ]
-
A.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
B.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
C.
nameInJapaneseKana
chosen
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.
hanjaName
Indicates that one entity is the Sino-Korean (hanja) written form corresponding to the name of another entity.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc104846c81908b6fbde7061464b4 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.