Triple
T26900840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yagi |
E678023
|
entity |
| Predicate | hasJapaneseNameKana |
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: [Yagi, hasJapaneseNameKana, やぎちょう]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJapaneseNameKana Context triple: [Yagi, hasJapaneseNameKana, やぎちょう]
-
A.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
B.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
C.
hasJapaneseSurname
Indicates that the person or entity possesses a surname that is of Japanese origin or is commonly used in Japanese naming conventions.
-
D.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
E.
nameInJapaneseKana
chosen
Indicates that an entity’s name is written or represented using Japanese kana 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61faf46448190bd49b472f805d52b |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:50 a.m.