Triple
T5639308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival City |
E124225
|
entity |
| Predicate | peakFestivalSeason |
P29256
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [Festival City, peakFestivalSeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakFestivalSeason Context triple: [Festival City, peakFestivalSeason, summer]
-
A.
festivalSeason
chosen
Indicates that a time period is designated or recognized as the season during which a particular festival or set of festivals takes place.
-
B.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
C.
peerFestival
Indicates that two festivals are considered peers, sharing a comparable status, scale, or role within a given context.
-
D.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
E.
shareCulturalFestivals
Indicates that two or more entities participate in or observe the same cultural festivals or celebrations.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c02283bb248190b29ac6255c78c5ec |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.