Triple
T9892937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōse |
E181497
|
entity |
| Predicate | hasScript |
P182
|
FINISHED |
| Object | Hiragana |
E3828
|
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: Hiragana | Statement: [Ōse, hasScript, Hiragana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hiragana Context triple: [Ōse, hasScript, Hiragana]
-
A.
Hiragana
chosen
Hiragana is a Japanese phonetic syllabary used primarily for native words, grammatical elements, and beginners’ reading and writing.
-
B.
Katakana
Katakana is one of the two main Japanese phonetic writing systems, primarily used for foreign words, onomatopoeia, emphasis, and technical or scientific terms.
-
C.
Kana
Kana is the Japanese syllabic writing system comprising hiragana and katakana, used to represent native words, grammatical elements, and foreign terms.
-
D.
Kana
Kana is a settlement located within Pakistan’s Shangla District in the Khyber Pakhtunkhwa province.
-
E.
Kanji
Kanji are logographic characters of Chinese origin used in the Japanese writing system alongside hiragana and katakana.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4814a3c8190ab1fd7f755a44508 |
completed | April 2, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eb0d984c81908408f90f156624e5 |
completed | April 5, 2026, 4:54 a.m. |
Created at: March 30, 2026, 8:39 p.m.