Triple
T8400736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man'yōgana |
E198162
|
entity |
| Predicate | hasTransliterationTarget |
P62529
|
FINISHED |
| Object | hiragana |
—
|
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: hiragana | Statement: [Man'yōgana, hasTransliterationTarget, hiragana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransliterationTarget Context triple: [Man'yōgana, hasTransliterationTarget, hiragana]
-
A.
hasTransliterationRole
Indicates that an entity participates in a transliteration process with a specific role (e.g., source, target, or agent of transliteration).
-
B.
hasTransliterationRule
Indicates that there exists a specific rule or mapping that defines how text in one script or writing system is systematically converted into another.
-
C.
transliterationTarget
chosen
Indicates that one entity is the target script or form into which another entity is transliterated.
-
D.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
E.
hasTitleInTransliteration
Indicates that an entity has a specific title represented in a transliterated form from another writing system.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824da3148190bfa3a1abfdfa02de |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.