Triple
T20145516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 元興寺 |
E491291
|
entity |
| Predicate | 主な行事 |
P83350
|
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.
majorFestivalFunction
Indicates that an entity serves as a primary or central function, role, or activity within a major festival.
-
B.
mainEvents
chosen
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
C.
isMajorEventOf
Indicates that an event is a primary, significant, or defining occurrence within the context of another entity (such as a project, period, or process).
-
D.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
E.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679e43a48190b3a5da5710b07ff7 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.