Triple
T32546017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazariyama |
E831848
|
entity |
| Predicate | hasRoleInFestival |
P28049
|
FINISHED |
| Object | symbol of local pride |
—
|
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: symbol of local pride | Statement: [Kazariyama, hasRoleInFestival, symbol of local pride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInFestival Context triple: [Kazariyama, hasRoleInFestival, symbol of local pride]
-
A.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasKeyFestival
Indicates that an entity is associated with a primary or central festival that is especially significant to it.
-
C.
hasFestivalConnection
Indicates a relationship in which two entities are connected through a festival, such as by participation, organization, sponsorship, or association with that event.
-
D.
hasFestivalContext
chosen
Indicates that something is related to, occurs within, or is characterized by the setting, activities, or circumstances of a festival.
-
E.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:02 a.m.