Triple
T21256235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waynesville, Ohio |
E523876
|
entity |
| Predicate | OhioSauerkrautFestivalHeldIn |
P26210
|
FINISHED |
| Object | October |
—
|
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: October | Statement: [Waynesville, Ohio, OhioSauerkrautFestivalHeldIn, October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OhioSauerkrautFestivalHeldIn Context triple: [Waynesville, Ohio, OhioSauerkrautFestivalHeldIn, October]
-
A.
festivalHeldIn
chosen
Indicates that a festival takes place or is hosted at a specific location or venue.
-
B.
festivalFoundedIn
Indicates that a festival was established or created in a specific year or time period.
-
C.
harvestFestival
Indicates a relationship where a community or group holds a celebratory event or ritual to mark and give thanks for the gathering of crops or agricultural produce.
-
D.
festivalObserved
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
E.
festivalFounded
Indicates that a particular festival was established or created by a specific person, group, or organization.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735a1f9e08190b494f582bcae5c35 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:58 p.m.