Triple
T19897845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inagawa River |
E478197
|
entity |
| Predicate | writtenInJapaneseKana |
P9812
|
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: [Inagawa River, writtenInJapaneseKana, いながわ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInJapaneseKana Context triple: [Inagawa River, writtenInJapaneseKana, いながわ]
-
A.
canBeWrittenAsKana
Indicates that something (typically text or a term) is able to be represented using Japanese kana characters.
-
B.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
C.
nameInJapaneseKana
chosen
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
D.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
E.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593ef8dc8190be5b64988eceafac |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.