Triple
T26551344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 梅花祭 |
E671684
|
entity |
| Predicate | 関連する宗教行事 |
P75655
|
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.
associatedWithReligiousEvent
chosen
Indicates a relationship where something is connected or related to a specific religious event or ceremony.
-
B.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
C.
religiousOrRitualAssociation
Indicates a connection between entities based on shared religious, spiritual, or ritual practices, roles, or significance.
-
D.
religiousObjectAssociated
Indicates that a religious object is associated with, connected to, or used in relation to another entity (such as a person, place, event, or practice).
-
E.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
- 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_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:47 a.m.