Triple
T36068697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōan |
E1043305
|
entity |
| Predicate | JapaneseSpelling |
P17917
|
FINISHED |
| Object | 保安 |
—
|
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: 保安 | Statement: [Hōan, JapaneseSpelling, 保安]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JapaneseSpelling Context triple: [Hōan, JapaneseSpelling, 保安]
-
A.
JapaneseNameReading
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other entity.
-
B.
typicalKanjiSpelling
Indicates that one written form is the standard or most commonly used kanji spelling for another expression (such as a word or phrase).
-
C.
onYomiJapanese
Indicates that the specified reading is the on’yomi (Sino-Japanese) pronunciation associated with a given kanji or term.
-
D.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
-
E.
kanji
chosen
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.