Triple
T33105100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中村 |
E847167
|
entity |
| Predicate | hasReadingRomaji |
—
|
GENERATED |
| Object | Nakamura |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReadingRomaji Context triple: [中村, hasReadingRomaji, Nakamura]
-
A.
hasReadingKana
Indicates that an entity is associated with a specific reading written in Japanese kana script.
-
B.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
-
C.
hasHakkaRomanization
Indicates that an entity is associated with a specific representation of its name or term in Hakka Romanization.
-
D.
hasRomanizationOf
chosen
Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
-
E.
hasHokkienReading
Indicates that an entity is associated with a specific reading or pronunciation in the Hokkien language.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.