Triple
T31943282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasure-House Gate |
E815581
|
entity |
| Predicate | japaneseReading |
P143799
|
FINISHED |
| Object | Hōzōmon |
—
|
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: Hōzōmon | Statement: [Treasure-House Gate, japaneseReading, Hōzōmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: japaneseReading Context triple: [Treasure-House Gate, japaneseReading, Hōzōmon]
-
A.
japaneseOnReading
Indicates the on-yomi (Sino-Japanese) pronunciation associated with a given Japanese kanji or term.
-
B.
JapaneseNameReading
chosen
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other entity.
-
C.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
-
D.
kanji
Indicates that an entity is written in, represented by, or associated with a specific kanji character or set of kanji characters.
-
E.
hasKanjiReading
Indicates that a written kanji character is associated with a specific reading or pronunciation.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2758cec8190b0521eb7f2eccb42 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:06 a.m.