Triple
T18564008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kana Supplement |
E453716
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | Kana_Sup |
—
|
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: Kana_Sup | Statement: [Kana Supplement, hasAbbreviation, Kana_Sup]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kana_Sup Context triple: [Kana Supplement, hasAbbreviation, Kana_Sup]
-
A.
Kana Supplement
chosen
Kana Supplement is a Unicode block that contains additional Japanese kana characters used for specialized phonetic and historical notation beyond the standard hiragana and katakana sets.
-
B.
Kana
Kana is the Japanese syllabic writing system comprising hiragana and katakana, used to represent native words, grammatical elements, and foreign terms.
-
C.
Kana
Kana is a settlement located within Pakistan’s Shangla District in the Khyber Pakhtunkhwa province.
-
D.
Kana Extended-B
Kana Extended-B is a Unicode block that contains additional Japanese kana characters used for specialized phonetic and historical writing systems.
-
E.
Small Kana Extension
Small Kana Extension is a Unicode block that adds additional small Japanese kana characters used for specialized phonetic and orthographic purposes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
Created at: April 10, 2026, 11:42 a.m.