Triple
T32546070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asayama morning runs |
E831850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | festival practice event |
C58663
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: festival practice event Context triple: [Asayama morning runs, instanceOf, festival practice event]
-
A.
festival
A festival is a planned, often recurring event where a community gathers to celebrate cultural, religious, seasonal, or thematic traditions through shared activities, performances, and rituals.
-
B.
festival performance
A festival performance is a scheduled live presentation of artistic or cultural expression—such as music, dance, theater, or multimedia—staged as part of a larger celebratory event or series.
-
C.
festival organization
Festival organization is the coordinated planning, management, and execution of all logistical, financial, promotional, and experiential aspects required to design and deliver a successful festival event.
-
D.
festival program
A festival program is a curated schedule and guide that outlines the events, performances, venues, and times for a festival, providing attendees with essential information to plan and navigate their experience.
-
E.
festival venue
A festival venue is a designated location equipped with the infrastructure, amenities, and spatial layout necessary to host large-scale, often multi-day cultural, musical, or artistic events for public audiences.
- F. None of above. chosen
Provenance (1 batch)
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.