Triple
T7134144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato people |
E166261
|
entity |
| Predicate | historicalScriptDevelopment |
P4037
|
FINISHED |
| Object | man’yōgana |
—
|
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: man’yōgana | Statement: [Yamato people, historicalScriptDevelopment, man’yōgana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalScriptDevelopment Context triple: [Yamato people, historicalScriptDevelopment, man’yōgana]
-
A.
historicalScript
chosen
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
B.
writingSystemHistorically
Indicates that one writing system was historically used for, associated with, or served as a predecessor to another writing system.
-
C.
writingSystemDevelopedFrom
Indicates that one writing system originated, evolved, or was derived from another earlier writing system.
-
D.
historicalLanguageFeature
Indicates that a language possesses a feature, trait, or characteristic that existed or was relevant in a past historical period.
-
E.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e68f15bc8190a4d82b8ee388f497 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.