Triple
T8400723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man'yōgana |
E198162
|
entity |
| Predicate | derivationProcess |
P51498
|
FINISHED |
| Object | simplification led to 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: simplification led to hiragana | Statement: [Man'yōgana, derivationProcess, simplification led to hiragana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivationProcess Context triple: [Man'yōgana, derivationProcess, simplification led to hiragana]
-
A.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
B.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
-
C.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
D.
developmentProcessIncludes
Indicates that a particular activity, phase, or component is part of, or contained within, a broader development process.
-
E.
originProcess
chosen
Indicates the process, activity, or mechanism from which an entity, condition, or outcome originally arises or is produced.
- 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.