Triple
T8887356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince (kōshaku) of the kazoku peerage |
E211565
|
entity |
| Predicate | romajiTranscription |
P2508
|
FINISHED |
| Object | kōshaku |
—
|
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: kōshaku | Statement: [Prince (kōshaku) of the kazoku peerage, romajiTranscription, kōshaku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romajiTranscription Context triple: [Prince (kōshaku) of the kazoku peerage, romajiTranscription, kōshaku]
-
A.
japaneseKunReading
Indicates that a Japanese kanji character has a specific native Japanese (kun) reading associated with it.
-
B.
translationOfJapaneseName
Indicates that one entity is a translation of a Japanese name given by the other entity.
-
C.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
D.
hasRomanizationOf
chosen
Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
-
E.
kanji
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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618d4c188190810d2e38591f515a |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.