Triple
T20037412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inoue |
E497312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese-language surname |
C14177
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Japanese-language surname Context triple: [Inoue, instanceOf, Japanese-language surname]
-
A.
Japanese given name
A Japanese given name is a personal name assigned at birth or during naming ceremonies in Japan, typically written in kanji, hiragana, or katakana, and often chosen for its meaning, sound, and cultural significance.
-
B.
East Asian surname
chosen
An East Asian surname is a family name originating from countries such as China, Japan, Korea, and neighboring regions, often carrying historical, linguistic, and cultural significance unique to those societies.
-
C.
Japanese honorific name
A Japanese honorific name is a personal name accompanied by a respectful suffix (such as -san, -sama, -kun, or -chan) that reflects the social relationship, status, and level of politeness between speaker and referent.
-
D.
Indonesian surname
An Indonesian surname is a family or inherited name used in Indonesia that may reflect ethnic, regional, religious, or cultural identity, though many Indonesians traditionally use single names without surnames.
-
E.
Japanese place name
A Japanese place name is a toponym used to identify a specific geographic location in Japan, often reflecting historical, cultural, or natural features through kanji characters and traditional naming conventions.
- F. None of above.
Provenance (1 batch)
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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:36 p.m.