Triple
T26551349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 梅花祭 |
E671684
|
entity |
| Predicate | 関連する歴史的背景 |
P1409
|
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.
historicalBackground
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
B.
hasHistoricalContext
chosen
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
C.
shareHistoricalContextAs
Indicates that two or more entities are associated with or understood within the same historical background, period, or circumstances.
-
D.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
E.
historicallyBasedOn
Indicates that something is derived from, inspired by, or modeled on historical events, sources, or precedents.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614624c80819084f6febf57f86828 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:47 a.m.