Triple
T36895468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fillmore Jazz District |
E911877
|
entity |
| Predicate | FillmoreJazzFestivalFrequency |
P78772
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Fillmore Jazz District, FillmoreJazzFestivalFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FillmoreJazzFestivalFrequency Context triple: [Fillmore Jazz District, FillmoreJazzFestivalFrequency, annual]
-
A.
hasJazzFestivalSince
Indicates that a location or entity has hosted or held a jazz festival continuously since a specified starting date or year.
-
B.
hasFestivalFrequency
chosen
Indicates how often a festival or recurring celebratory event takes place within a given time period.
-
C.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
D.
exhibitionFrequency
Indicates how often an entity is displayed, presented, or exhibited within a given context or time period.
-
E.
convenesEveryNumberOfYears
Indicates that an event or body formally gathers or meets at regular intervals defined by a specific number of years.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd8d3ad08190854b227055102a89 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.