Triple
T29215208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 柿本人麻呂 |
E740648
|
entity |
| Predicate | 後世への影響 |
P40703
|
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.
hasEnduringInfluence
Indicates that one entity continues to significantly affect, shape, or inform another entity or context over an extended period of time.
-
B.
hasEnduringInfluenceOn
chosen
Indicates that one entity exerts a lasting, long-term impact on another entity’s state, development, or behavior.
-
C.
heritageInfluence
Indicates how one entity’s cultural, historical, or ancestral background affects or shapes another entity’s characteristics, behavior, or development.
-
D.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
E.
influencedGenerationOf
Indicates that one entity played a causal or shaping role in bringing about, inspiring, or contributing to the creation or emergence of another entity.
- 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.