Triple
T15803405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 趙 |
E383150
|
entity |
| Predicate | JapaneseOnReading |
P51401
|
FINISHED |
| Object | Chō |
—
|
LITERAL 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: Chō | Statement: [趙, JapaneseOnReading, Chō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JapaneseOnReading Context triple: [趙, JapaneseOnReading, Chō]
-
A.
japaneseOnReading
chosen
Indicates the on-yomi (Sino-Japanese) pronunciation associated with a given Japanese kanji or term.
-
B.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
-
C.
JapaneseFormation
Indicates a relationship where something is formed, created, or organized according to Japanese style, methods, or origin.
-
D.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
E.
hasMandarinReading
Indicates that an entity is associated with a specific reading or pronunciation in Mandarin Chinese.
- F. None of above.
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b524835c8190ae286b2562f07756 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.