Triple
T29215199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 柿本人麻呂 |
E740648
|
entity |
| Predicate | 文学史上の位置づけ |
P15594
|
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: [柿本人麻呂, 文学史上の位置づけ, 歌聖と称されることがある]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 文学史上の位置づけ Context triple: [柿本人麻呂, 文学史上の位置づけ, 歌聖と称されることがある]
-
A.
hasLiterarySignificance
chosen
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
B.
historiographicalStatus
Indicates the recognized standing or classification of something within historical writing or scholarship, such as how it is interpreted, debated, or valued by historians.
-
C.
hasReputationInLiterature
Indicates that an entity is recognized or regarded in a particular way within literary works or the field of literature.
-
D.
literaryMovementReception
Indicates how a particular literary movement has been received, interpreted, or evaluated by critics, audiences, or later literary traditions.
-
E.
literaryInfluence
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66408d068819082a94491d663bff2 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:13 p.m.