Triple
T30640060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 加藤氏 |
E779949
|
entity |
| Predicate | usesKanji |
P17917
|
FINISHED |
| Object | 加藤 |
—
|
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: 加藤 | Statement: [加藤氏, usesKanji, 加藤]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesKanji Context triple: [加藤氏, usesKanji, 加藤]
-
A.
usesKanjiFrom
Indicates that one writing system, word, or text incorporates or is composed of kanji characters originating from another specified source.
-
B.
kanji
chosen
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
C.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
-
D.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
E.
commonKanjiComponent
Indicates that two or more kanji share a common graphical component or radical in their written form.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a5475f48190b0fcb96b90e470f2 |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.