Triple
T19164795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyajima |
E469150
|
entity |
| Predicate | hasJapaneseOfficialName |
P9882
|
FINISHED |
| Object | 厳島 |
—
|
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: 厳島 | Statement: [Miyajima, hasJapaneseOfficialName, 厳島]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJapaneseOfficialName Context triple: [Miyajima, hasJapaneseOfficialName, 厳島]
-
A.
hasOfficialNameInJapanese
chosen
Indicates that an entity has an official, formally recognized name expressed in the Japanese language.
-
B.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
C.
officialNameInRomaji
Indicates that an entity’s official name is written using the Roman alphabet (romaji) representation.
-
D.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
E.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f15e2720819084b1707497db26a2 |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.