Triple
T6060812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amami language |
E135027
|
entity |
| Predicate | hasWritingSystem |
P454
|
FINISHED |
| Object | Japanese kana |
E175376
|
NE 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: Japanese kana | Statement: [Amami language, hasWritingSystem, Japanese kana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Japanese kana Context triple: [Amami language, hasWritingSystem, Japanese kana]
-
A.
Katakana
Katakana is one of the two main Japanese phonetic writing systems, primarily used for foreign words, onomatopoeia, emphasis, and technical or scientific terms.
-
B.
Hiragana
Hiragana is a Japanese phonetic syllabary used primarily for native words, grammatical elements, and beginners’ reading and writing.
-
C.
Kanji
Kanji are logographic characters of Chinese origin used in the Japanese writing system alongside hiragana and katakana.
-
D.
Kana
chosen
Kana is the Japanese syllabic writing system comprising hiragana and katakana, used to represent native words, grammatical elements, and foreign terms.
-
E.
Bugis script
Bugis script is a traditional Brahmic writing system used primarily for the Buginese language of South Sulawesi, Indonesia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0571fcecc8190a68e0d0668bbbfa7 |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d197dd08190bcc6904c7c2e41aa |
completed | March 23, 2026, 10:59 a.m. |
Created at: March 22, 2026, 4:10 p.m.